keanmiller.com website review

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

4 images could be 657 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

Your mobile performance score is 61 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

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

About 331 KiB of JavaScript is downloaded but never used on this page.

FontAwesome CDN costs a phone 0 ms of main-thread work and 294 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.

4 third-party services load with your homepage (Optanon, JSDelivr CDN and Google Fonts and others), adding 713 KiB and 100 ms of main-thread time.

134 KiB could be saved by minifying JavaScript.

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

2 long tasks block the main thread while loading, the longest for 52 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).

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

6 KiB could be saved by minifying CSS.

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.

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

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

Your largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Just as oil and gas must be refined to unlock their true po…”.

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

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

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

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

2 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-24, real Chrome visitors' tap response (inp) went from 76 ms to 73 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.3 MB in 50 requests on a phone: images 2.3 MB (10), scripts 536 KiB (14) and fonts 441 KiB (9). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (28 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 0.95 g of CO₂e: 113.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 2 <h1> headlines (“Rethink. Refine. Rediscover.” and “Diversity in action”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://www.keanmiller.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 29 pages on keanmiller.com and 9 external pages.

https://www.keanmiller.com/insights and https://www.keanmiller.com/news use the same meta description. A description written for each page earns more clicks.

https://www.keanmiller.com/team, https://www.keanmiller.com/services-industries, https://www.keanmiller.com/insights, https://www.keanmiller.com/careers, https://www.keanmiller.com/news and https://www.keanmiller.com/about-kean-miller took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “jQuery is not defined”.

Large scripts ship without source maps.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 175 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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