tayloegray.com website review

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

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

13 files are served with short cache lifetimes, so returning visitors download them again (3.1 MB).

7 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Clarity and others), adding 1.4 MB and 791 ms of main-thread time.

Google CDN costs a phone 349 ms of main-thread work and 755 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 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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.

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 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

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

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

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

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

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

Your homepage downloads 8.3 MB in 90 requests on a phone: media 3.8 MB (1), images 2.2 MB (25) and scripts 1.5 MB (33). Under 2 MB keeps phones on slow connections fast.

2 images (78 KiB) are 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.

3 images further down the page (99 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 49 pages on tayloegray.com and 21 external pages.

There is no https://www.tayloegray.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.

https://www.tayloegray.com/our-work, https://www.tayloegray.com/about, https://www.tayloegray.com/blog, https://www.tayloegray.com/contact, https://www.tayloegray.com/our-work/mickey-truck-bodies and https://www.tayloegray.com/our-work/maxpro-window-films and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tayloegray.com/contact and https://www.tayloegray.com/our-clients have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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 729 words of visible text.

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

Opening the homepage sets 4 cookies, 2 of them by other companies (measured from a US location before any click).

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