zerotodigital.com website review

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

7 images could be 1.1 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 75. Pages that score under 90 lose visitors before the first paint.

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

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

4 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Fonts and others), adding 256 KiB and 185 ms of main-thread time.

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

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

About 14 KiB of CSS is downloaded but never applied on this page.

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.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Help your business work for AI agents.”. Most of its time is element render delay (4.1 s).

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

abstract-systems.png weighs 981 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.1 MB in 46 requests on a phone: images 1.8 MB (33), scripts 190 KiB (4) and fonts 82 KiB (4). Under 2 MB keeps phones on slow connections fast.

9 images (1.5 MB) 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.

12 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images are downloaded at several times the size a phone draws them, for example rhi-2.png at 434 px wide, shown at 44 px. Resized copies would save about 340 KiB.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

2 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 69 characters, so Google will cut it off around 60: “Tyler Willis — Help Your Business Work for AI Agents | Author of OARS”.

Your meta description is 232 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 67 pages on zerotodigital.com and 10 external pages.

https://tylerewillis.com/blog has no meta description, so Google writes the search snippet from whatever text it finds.

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

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 1,951 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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