formulaeprescott.com website review

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

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

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

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

8 third-party services load with your homepage (Yotpo, Google Tag Manager and nice-team.net and others), adding 1.6 MB and 1.0 s of main-thread time.

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

About 123 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.

Yotpo costs a phone 373 ms of main-thread work and 672 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.

116 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 324 ms of main-thread work and 350 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.

6 images could be 44 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

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

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

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 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

1 image 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 3.5 MB in 253 requests on a phone: scripts 1.9 MB (76), other files 754 KiB (102) and images 520 KiB (46). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (73 KiB) 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 0.98 g of CO₂e: 117.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

1 element hidden from screen readers can still receive keyboard focus.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

1 button has no accessible name, so screen readers announce just “button”.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 50 pages on formulaeprescott.com and 10 external pages.

https://formulaeprescott.com/en-us/blogs/news is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://formulaeprescott.com/en-us/collections/shop-all, https://formulaeprescott.com/en-us/pages/reviews, https://formulaeprescott.com/en-us/pages/rewards, https://formulaeprescott.com/en-us/blogs/news, https://formulaeprescott.com/en-us/collections/all and https://formulaeprescott.com/en-us/collections/tri-balm have no meta description, so Google writes the search snippet from whatever text it finds.

https://formulaeprescott.com/en-us/collections/shop-all, https://formulaeprescott.com/en-us/pages/our-story, https://formulaeprescott.com/en-us/pages/reviews, https://formulaeprescott.com/en-us/pages/rewards, https://formulaeprescott.com/en-us/blogs/news and https://formulaeprescott.com/en-us/pages/contactus and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://track.sweetanalytics.com/event.gif?1=1&uid=e8531dacb26c865963b210483056bc04&cid=AT-64df4b29452a9&pt=Natural%20Multitasking%20Skincare%20%E2%80%93%20FP&hn=https%3A%2F%2Fformulaeprescott.com%2Fe.

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: productRecommendations is not defined”.

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

1 image is served at too low a resolution for sharp phone screens.

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 390 words of visible text.

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