jeejeebhoy.ca website review

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

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

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

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

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

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

6 third-party services load with your homepage (StatCounter, FontAwesome CDN and WordPress Site Stats and others), adding 418 KiB and 82 ms of main-thread time.

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

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

Desktop scores 86 but mobile only 59. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

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

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

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

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

Your homepage downloads 2.5 MB in 109 requests on a phone: images 1.4 MB (15), fonts 506 KiB (9) and scripts 287 KiB (30). Under 2 MB keeps phones on slow connections fast.

7 images (882 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.

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

4 images are downloaded at several times the size a phone draws them, for example https://substack-post-media.s3.amazonaws.com/public/images/6 at 3,200 px wide, shown at 150 px. Resized copies would save about 433 KiB.

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

[role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

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

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

There are 3 <h1> headlines (“Shireen Anne Jeejeebhoy”, “Reading, Writing, Photography” and “Concussion Is Brain Injury”). One clear main headline is easier for people and search engines.

11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 54 pages on jeejeebhoy.ca and 36 external pages.

Your Organization JSON-LD is missing url, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://jeejeebhoy.ca/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.

Your homepage links to https://jeejeebhoy.ca/shop, which answers with an error. Visitors hit a dead end and search engines drop it.

https://jeejeebhoy.ca/blog, https://jeejeebhoy.ca/library/lifeliner/readings, https://jeejeebhoy.ca/library/lifeliner/photo-gallery, https://jeejeebhoy.ca/library/lifeliner/book-club-questions and https://jeejeebhoy.ca/library/lifeliner/translation have no meta description, so Google writes the search snippet from whatever text it finds.

https://jeejeebhoy.ca/compositionally-yours took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 42 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: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The page uses urgency cues (a countdown or limited-time wording).

Opening the homepage sets 1 cookie (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.