phyto-c.com website review

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

32 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.2 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Clarity, Shopify and Klaviyo and others), adding 1.4 MB and 815 ms of main-thread time.

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

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

Shopify costs a phone 151 ms of main-thread work and 429 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.

Klaviyo costs a phone 148 ms of main-thread work and 369 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.

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

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

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

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

9 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Soothing Power Meets Clinical PrecisionFormulas tested to h…”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.1 MB in 379 requests on a phone: scripts 1.5 MB (106), images 1.1 MB (71) and other files 950 KiB (133). Under 2 MB keeps phones on slow connections fast.

banner-model.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

1 image is downloaded at several times the size a phone draws it, for example Img_1_ad555c74-ccc8-4ba9-8212-d5ebb5509cca.png at 953 px wide, shown at 290 px. Resized copies would save about 11 KiB.

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

3 buttons have no accessible name, so screen readers announce just “button”.

5 elements hidden from screen readers can still receive keyboard focus.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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.

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

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

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h6, h1 → h5 and h3 → h6), which makes the page harder to scan with a screen reader.

Your title is 66 characters, so Google will cut it off around 60: “Phyto-C Skin Care - Leaders in Vitamin C Serums & Natural Products”.

There are 2 <h1> headlines (“” and “Soothing Power Meets Clinical Precision”). One clear main headline is easier for people and search engines.

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

6 links have no real href, so search engines can't follow them.

The homepage links to 122 pages on phyto-c.com and 7 external pages.

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

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

https://www.phyto-c.com/customer_authentication/redirect, https://www.phyto-c.com/policies/shipping-policy, https://www.phyto-c.com/pages/find-your-routine and https://www.phyto-c.com/collections/creams have no meta description, so Google writes the search snippet from whatever text it finds.

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

https://www.phyto-c.com/collections/bestsellers 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.

6 of 27 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.”).

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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 23 cookies, 1 of them by other companies (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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.