jefferspet.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Accessibe Accessibility Overlay and buildwithtoki.com and others), adding 1.8 MB and 928 ms of main-thread time.

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

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

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

Shopify costs a phone 395 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.

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

14 KiB could be saved by minifying JavaScript.

2 images could be 11 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Jeffers expression Pre-orders open - space background”.

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

The first text or image appears after 3.5 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.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 141 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 255 requests on a phone: other files 1.6 MB (144), scripts 1.5 MB (88) and HTML 199 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example JeffersLogo_Default_Red_512px_eb31eb30-7265-48ea-9e41-e01f32 at 502 px wide, shown at 140 px. Resized copies would save about 36 KiB.

3 images (249 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.

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

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

8 tap targets are too small or too close together to hit reliably with a finger.

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

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.

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

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. (8 elements).

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

The homepage links to 998 pages on jefferspet.com and 0 external pages.

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.

https://jefferspet.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://jefferspet.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

https://jefferspet.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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 400 ()”.

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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.

The homepage carries about 1,878 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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 15 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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.