paleolf.us website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and paleolf.com and others), adding 957 KiB and 639 ms of main-thread time.

19 images could be 516 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.

About 489 KiB of JavaScript is downloaded but never used on this page.

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

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

Klaviyo costs a phone 131 ms of main-thread work and 309 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 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.

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

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

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

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

2 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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 16.6 MB in 283 requests on a phone: media 12.1 MB (3), images 2.2 MB (58) and scripts 1.3 MB (92). Under 2 MB keeps phones on slow connections fast.

imagen_producto_ZIM.webp weighs 499 KiB. On a phone connection a single image that size takes seconds.

13 images (2.1 MB) 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.

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

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

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

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

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

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

Your title is 85 characters, so Google will cut it off around 60: “Premium Vitamin Supplements 100% Natural Highest Purity and Absorption – Paleolife US”.

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

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

Your <h1> is empty.

The homepage links to 153 pages on paleolf.us and 14 external pages.

There is no https://paleolf.us/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.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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