michaelhalsey.dev website review

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

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

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

6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.5 MB and 776 ms of main-thread time.

Google CDN costs a phone 591 ms of main-thread work and 1.1 MB 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.

1 image could be 281 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

Your largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Home Portfolio Your Vision. My Expertise. Let's Create. Cus…”.

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

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

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.

Your homepage downloads 3.8 MB in 31 requests on a phone: images 1.9 MB (7), scripts 1.2 MB (7) and other files 353 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

We fetched 1 page linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://fonts.googleapis.com/css2?family=Blinker:wght@100;200;300;400&display=swap' violates the followi…”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 331 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 2 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.