exoprotein.com website review

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

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

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

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

8 third-party services load with your homepage (Signyfyd, amaicdn.com and Google CDN and others), adding 1.7 MB and 1.8 s of main-thread time.

Signyfyd costs a phone 893 ms of main-thread work and 280 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.

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

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

amaicdn.com costs a phone 257 ms of main-thread work and 404 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 213 ms of main-thread work and 379 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 299 requests on a phone: scripts 1.8 MB (91), other files 879 KiB (155) and images 643 KiB (33). Under 2 MB keeps phones on slow connections fast.

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

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

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

Some list items are not inside a list.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 11 characters: “EXO Protein”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (HealthAndBeautyBusiness, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 45 pages on exoprotein.com and 4 external pages.

/pages/sustainability and /blogs/sustainability all use the title “Sustainability - EXO Protein”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/breakfast-bars, /pages/sustainability and /blogs/landing have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/featured/products/peanut-butter-chocolate-protein-bar and /products/peanut-butter-chocolate-protein-bar use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /collections/featured/products/peanut-butter-chocolate-protein-bar, whose canonical is /products/peanut-butter-chocolate-protein-bar. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/blogs/landing, /blogs/nutrition, /blogs/sustainability and /blogs/recipes have no <h1> headline, so visitors and search engines get no clear main topic.

/blogs/landing has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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

11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

1 link to other sites is dead, for example https://hoppyplanetfoods.faire.com/ (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

exoprotein.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

exoprotein.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

exoprotein.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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.

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

exoprotein.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be exoprotein.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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