jimallen.com website review

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

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

Your mobile performance score is 31 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

The page has 3,182 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

25 images could be 7.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Hubspot and others), adding 5.8 MB and 2.4 s of main-thread time.

Google Tag Manager costs a phone 583 ms of main-thread work and 736 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 CDN costs a phone 497 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.

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

hsappstatic.net costs a phone 420 ms of main-thread work and 697 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.

Hubspot costs a phone 424 ms of main-thread work and 376 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.

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

Vimeo costs a phone 63 ms of main-thread work and 2.5 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.

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

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

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.

For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.

Your largest element takes 42.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

Your homepage downloads 18.3 MB in 236 requests on a phone: images 11.6 MB (72), scripts 3.8 MB (74) and other files 2.3 MB (58). Under 2 MB keeps phones on slow connections fast.

7 images weigh 5.5 MB together. On a phone connection a single image that size takes seconds.

17 images are downloaded at several times the size a phone draws them, for example 20260914151048054628000000-o.jpg at 3,000 px wide, shown at 350 px. Resized copies would save about 5.8 MB.

26 images (8.3 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.

15 images further down the page (1.7 MB) 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 5.18 g of CO₂e: 621.1 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.

1 frame has no title, so screen-reader users cannot tell what it contains.

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.

13 form fields have no label, so screen readers announce an empty box and autofill guesses.

7 visible links have no text or label, so screen readers cannot say where they go.

No meta description, so Google writes its own snippet from whatever text it finds.

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

The homepage links to 115 pages on jimallen.com and 14 external pages.

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

1 image failed to load on a phone, for example https://www.jimallen.com/.

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

Chrome logged issues while loading the page (“Cookie”).

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

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.

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

The homepage carries about 2,979 words of visible text.

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

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

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