sitetracker.com website review

14 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.

13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.3 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1.4 MB and 1.8 s of main-thread time.

24 files are served with short cache lifetimes, so returning visitors download them again (563 KiB).

About 684 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

Google Tag Manager costs a phone 782 ms of main-thread work and 570 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 98 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

Facebook costs a phone 277 ms of main-thread work and 224 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

18 long tasks block the main thread while loading, the longest for 249 ms. During a long task the page ignores taps.

Polyfills for old browsers add 48 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

The page becomes fully interactive after 18.1 s. Good is under 3.8 s.

Visually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 894 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

The layout shifts by 0.141 while loading, so content jumps under the reader's thumb. Good is under 0.1.

21 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 151 ms to 159 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.4 MB in 141 requests on a phone: media 9.3 MB (2), scripts 1.5 MB (45) and images 1.2 MB (37). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example new-planning-development.gif at 1,280 px wide, shown at 252 px. Resized copies would save about 183 KiB.

1 image (281 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (281 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 3.50 g of CO₂e: 420.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (1 element).

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

The homepage links to 85 pages on sitetracker.com and 6 external pages.

There is no https://www.sitetracker.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.sitetracker.com/products-services/agreement-management, whose canonical is https://www.sitetracker.com/products-services/agreement-management?lang=de. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.sitetracker.com/products-services/field-work-management, https://www.sitetracker.com/products-services/site-asset-management and https://www.sitetracker.com/products-services/reporting-analytics took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25055786&tm=gtm002&Ver=2&mid=1125c12a-eb87-44bc-90d7-289efe4ac817&bo=1&sid=c175e3e0d6d711f1bc15411dbd7f97bd&vid=c1760d40d6d711f18b1dc34920e33f16&vids=1&msclkid=N&pi=91.

3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 530 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 27 cookies (measured from a US location before any click).

Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.