skratchlabs.com website review

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

A phone's processor spends 5.1 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 69. Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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

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

Shopify costs a phone 156 ms of main-thread work and 518 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,701 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

28 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 28 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 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “skratch labs sample pack box”.

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

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

11 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 131 ms to 128 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 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 18.8 MB in 443 requests on a phone: media 13.7 MB (3), images 1.8 MB (69) and other files 1.6 MB (257). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example a9e9f40d-4512-40b5-825f-7a9c92d4324f.jpeg at 800 px wide, shown at 177 px. Resized copies would save about 50 KiB.

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

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

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

All page content should be contained by landmarks: 7 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.

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

Your title is 68 characters, so Google will cut it off around 60: “Skratch Labs | Hydration, Nutrition, Recovery, Energy - Skratch Labs”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Skratch Labs” and “Skratch Labs”). One clear main headline is easier for people and search engines.

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

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 186 pages on skratchlabs.com and 7 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.

There is no https://www.skratchlabs.com/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.

https://www.skratchlabs.com/pages/skratch-guarantee, https://www.skratchlabs.com/products/energy-chews-sport-fuel, https://www.skratchlabs.com/products/hydration-sport-drink-mix, https://www.skratchlabs.com/collections/hydration and https://www.skratchlabs.com/products/energy-bar-sport-fuel have no <h1> headline, so visitors and search engines get no clear main topic.

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

15 of 35 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.”).

2 errors were logged to the browser console while the page loaded, for example “Error: <path> attribute d: Unexpected end of attribute. Expected number, "…3.1 150 1.7-46.5".”.

Social proof on the homepage: 25 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage carries about 728 words of visible text.

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