xSpeed Cache is officially live! Get 50% OFF during Launch Week — Lifetime starts at just $79Lifetime from $79 — 50% OFF, Launch Week! See Plans →

See Plans →
Get Plugin xSpeed Hub
All features Cloudflare EnterpriseAdd-on

By what you run

WooCommerce storesAgencies & freelancersBlogs & publishersElementor & page buildersMembership & LMSAI & agents

By your business

Home & trade services 3 Food & hospitality 4 Health & wellness 5 Professional services 5 Retail & ecommerce 5 Creative & events 4 Publishing & media 4 Learning & community 4 Tech & agencies 3 With your AI agent All use cases & industries
xSpeed Hub Pricing Docs Blog Scan
Free vs Pro Compare Showcase Coverage Support Community
Appearance
Get Plugin
78of 100

ultrateam.bg

Scanned Sat, 03 Oct 2026 06:47:59 GMT · https://ultrateam.bg/ · scanned 2 times — see history

CLevel 4 · Fast
Scan a different site ›
Desktop view of ultrateam.bg at scan time. Click for full size
As Lighthouse saw it · click to enlarge
586msTTFB
90Lighthouse desktop · graded
89Lighthouse mobile
772msLCP
0.00CLS
brCompression
MISSCache

Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 78 (C) —

Real visitors (Chrome UX Report) Not enough Chrome traffic for field data on this page or its site, so only the lab run above is available.
Why is this different from the score in my browser?

The graded score is the desktop run. Lighthouse 13.5.0 runs at Google through the PageSpeed Insights API on a desktop profile with no CPU or network throttling — close to what Chrome DevTools on a laptop, GTmetrix's default test and the PageSpeed API (which defaults to desktop) all measure, so this is the number you should be able to reproduce: run it yourself on PageSpeed Insights.

Google ranks on mobile. That run happens too, on an emulated mid-range Android with a 4× CPU slowdown and a throttled connection, and the same page routinely scores 30–50 points lower there. Neither number is wrong — they are different tests. On this page the mobile run scored 78 (C) against 78 (C) here — to see every check graded on that run.

Lighthouse also varies a few points run to run on the same URL. Treat a trend across several scans as the signal, never a single digit.

Lab data: Google PageSpeed Insights (Lighthouse, desktop). Server probes (TTFB, compression, cache, headers) are measured separately from Vilnius, Lithuania (EU).

Lab performance (Lighthouse)B89 4/5 checks passed · 35.7/40 pts Jump to section ↓ Server response & cachingD68 2/4 checks passed · 13.5/20 pts Jump to section ↓ Asset optimizationD63 2/4 checks passed · 10/16 pts Jump to section ↓

Top fixes ranked by points recovered · desktop

Act on this report with your AI assistant

  1. ✓Platform detectedNot conclusively identified — every check below links the official guideline for its fix, valid on any stack.
  2. →Act on it with your AIThe machine-readable twin of this report gives an agent every failing check with its evidence, remediation and guideline link.
  3. →Check the originHosting sets the floor on TTFB. xCloud hosts any stack — agent/MCP access built in, bring-your-own-server pricing.

This does not look like a WordPress site, so xSpeed cannot automate the fixes directly — but Every check below links its official guideline, and the machine-readable twin of this report gives an AI everything it needs to plan the work (7 checks name a concrete remediation):

Read the speed report at https://xspeedcache.com/scan/r/ultrateam-bg-3c22f1e8a0.md — it lists every failing check with evidence and the official guideline for the fix. Produce a prioritized fix plan for my stack, apply what you can, then re-test by POSTing {"url":"https://ultrateam.bg/"} to https://xspeedcache.com/api/scan and compare the scores.
How the checks are graded Scan another site
Hosting is half of every score. Whatever the stack, the server behind it sets the floor on TTFB. xCloud — from the team behind xSpeed — hosts any platform (this site's own scanner runs on it), with agent/MCP access built in and bring-your-own-server pricing. Explore xCloud.host →

Connect this scanner to your AI assistant

Free. No API key, no sign-up. Scan any public site and get the same graded report as this one, with the fix for every failing check.

Endpoint

https://xspeedcache.com/scan/mcp

Claude Code — one command

claude mcp add --transport http xspeed-scan https://xspeedcache.com/scan/mcp

Claude Desktop, Cursor, or any MCP client — add to your config

{ "mcpServers": { "xspeed-scan": { "type": "http", "url": "https://xspeedcache.com/scan/mcp" } } }
  • run_speed_scan Scan any public URL and return this whole graded report.
  • get_speed_scan Read a scan already run, by its id.
Read the MCP documentation →
B

Lab performance (Lighthouse)

4/5 checks passed · 35.7/40 pts earned
89/100
Pass
Lighthouse performance score (desktop) 16.2/18 pts
90/100 (Lighthouse 13.5.0, desktop)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 772ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Cumulative Layout Shift ≤ 0.1 5/5 pts
CLS 0.004
Guidelines: web.dev — Cumulative Layout Shift
Partial
Total Blocking Time ≤ 200ms 2.5/5 pts
TBT 234ms
Less JavaScript on the main thread: defer scripts and drop unused bundles.
xSpeed Free JS Minify + Defer
AI promptUsing my site's xSpeed MCP connection: enable JS minification and deferred loading, then re-test Total Blocking Time.
Guidelines: web.dev — Total Blocking Time
Pass
First Contentful Paint ≤ 1.8s 4/4 pts
FCP 366ms
Guidelines: web.dev — First Contentful Paint
D

Server response & caching

2/6 checks passed · 13.5/20 pts earned
68/100
Partial
Time to first byte ≤ 200ms 4/8 pts
TTFB 586ms measured from Vilnius, Lithuania (EU) (best of 2 requests). This includes the network round trips between us and your origin, not just server time. Google measured your server responding in 68ms from its own network — the gap between the two numbers is distance, not your server.
The server rebuilds the page on every request. A page cache answers in 5–15ms.
xSpeed Free Page Cache
AI promptUsing my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.
Guidelines: web.dev — Time to First Byte
N/A
Page served from cache —
Correctly per-visitor — this response is marked `no-cache, must-revalidate, max-age=0, no-store, private`, so it must not be held in a shared cache.
Nothing to fix. If parts of this page are the same for everyone, they can still be cached separately — but the page as a whole is right to opt out.
Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: br
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Partial
Efficient cache policy on static assets 2.5/5 pts
Lighthouse cache-policy audit score 50% — 4 files: 1188534534997280 (connect.facebook.net), fbevents.js (connect.facebook.net), analytics.js (google-analytics.com)…
Every asset with a short cache lifetime here is served by another host (connect.facebook.net, google-analytics.com, facebook.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
xSpeed Free Browser Cache
AI promptUsing my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.
Guidelines: Lighthouse — Efficient cache policy
Info
CDN edge serves the page —
No CDN signature detected
Optional: put a CDN or Cloudflare in front for global edge delivery.
xSpeed Free Cloudflare integration / CDN rewriter
AI promptUsing my site's xSpeed MCP connection: connect Cloudflare (or configure the CDN rewriter) and purge, then re-scan.
Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
D

Asset optimization

2/5 checks passed · 10/16 pts earned
63/100
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 8 files: normalize.min.css, global-settings.css, custom_font_ultra_team.css… · ~400ms of first paint
CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
xSpeed Pro Critical CSS + Unused CSS removal
AI promptUsing my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.
Guidelines: Lighthouse — Render-blocking resources
Pass
Minified CSS and JavaScript 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Pass
Modern, optimized image formats 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Modern image formats
Info
LCP image discoverable early —
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Free Resource Hints (preload) + Lazy Load exclusions
AI promptUsing my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.
Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Partial
Total page weight (≤ 350KB for full marks) 2/3 pts
872KB transferred — above 350KB, where most WordPress pages fail mobile LCP
Page weight is what decides mobile LCP once the server is fast. Resize images to the size they display at, lazy-load below the fold, and drop scripts the page does not use.
xSpeed Free Minify + Lazy Load + Image Converter (Pro)
AI promptUsing my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.
Guidelines: Lighthouse — Total byte weight

Past scans of ultrateam.bg newest first · every report keeps its link

ScannedScoreGradeGraded onTTFBLighthouse
2026-10-03 06:47 UTC this report 78 C desktop 586ms 90
2026-10-03 06:42 UTC 75 C desktop 206ms 81 View report →

Share your score a card for X, LinkedIn, Slack — anywhere

Every check here has a one-click fix in xSpeed Cache

Page caching, compression, image optimization and a built-in MCP server, so your AI assistant can run this playbook for you.

Get xSpeed Cache Scan another site
Scan ultrateam-bg-3c22f1e8a0 · rubric v2026.10.1 · Lab data: Google PageSpeed Insights (Lighthouse 13.5.0), graded on the desktop run; the mobile run is graded on its tab · Server probes from xspeedcache.com. Scores vary run to run; treat trends, not single digits, as the signal. Markdown for AI agents · JSON
Own ultrateam.bg and would rather this report were not public? Email support@wpdeveloper.com and we will remove it.