mobilityware.com website review

About 593 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and cloudfront.net and others), adding 1.3 MB and 802 ms of main-thread time.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

19 images could be 602 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

The page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.

The HTML itself could arrive about 500 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

Google/Doubleclick Ads costs a phone 315 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.

Google Tag Manager costs a phone 279 ms of main-thread work and 318 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.

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

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

Polyfills for old browsers add 7 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.

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.

Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By continuing to use our site, you agree to our Cookie Noti…”.

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

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

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

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

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

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

Your homepage downloads 2.6 MB in 97 requests on a phone: scripts 1.3 MB (29), images 1.2 MB (47) and other files 47 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

6 tap targets are too small or too close together to hit reliably with a finger.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Heading elements are not in a sequentially-descending order (1 element).

No meta description, so Google writes its own snippet.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

We could not load https://mobilityware.com from our server, so the homepage checks are missing. If the site is up, it may block automated visitors.