Website review, no card needed
perfectketo.com website review
Visit site (opens in a new tab)Reviewed 5 November 202642 issues · 86 checks
This review found 42 issues worth fixing on perfectketo.com, 14 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80B- #45,332 of 114,375 reviewed websitesbeats 55%
- #30,618 of 66,168 online storesbeats 47%
- #29,503 of 60,561 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 163 ms |
| May 23, 2026 | 161 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 164 ms |
| Jul 4, 2026 | 168 ms |
| Jul 11, 2026 | 167 ms |
| Jul 18, 2026 | 168 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 168 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 168 ms |
| Aug 22, 2026 | 167 ms |
| Aug 29, 2026 | 163 ms |
| Sep 5, 2026 | 158 ms |
| Sep 12, 2026 | 159 ms |
| Sep 19, 2026 | 167 ms |
| Sep 26, 2026 | 174 ms |
| Oct 3, 2026 | 184 ms |
| Oct 10, 2026 | 185 ms |
| Oct 17, 2026 | 184 ms |
| Oct 24, 2026 | 185 ms |
| Oct 31, 2026 | 182 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
2.1 s
3.1 s
4.2 s
5.2 s
6.2 s
7.3 s
8.3 s
Speed
Render-blocking requests
3.2 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.2 s.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.1 s
A phone's processor spends 6.1 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
250 ms · 1.8 MB16 images could be 1.8 MB 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and hu-manity.co and others), adding 1.6 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
700 ms · 320 KiB21 files are served with short cache lifetimes, so returning visitors download them again (320 KiB).
Google Tag Manager adds 931 ms
931 msGoogle Tag Manager costs a phone 931 ms of main-thread work and 713 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.
Reduce unused CSS
600 ms · 137 KiBAbout 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Legacy JavaScript
400 ms · 98 KiBPolyfills for old browsers add 98 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 410 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 27 KiB27 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 24 KiB24 KiB could be saved by minifying CSS.
Duplicated JavaScript
150 ms · 23 KiB23 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 19.0 s
19.0 sYour largest element takes 19.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 33.2 s
33.2 sThe page becomes fully interactive after 33.2 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Real-user TTFB: 918 ms
918 msReal visitors wait 918 ms for your server to start answering (75th percentile). Good is under 800 ms.
36 images without width and height
36 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 163 ms to 182 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 19.8 MB in 186 requests
19.8 MBYour homepage downloads 19.8 MB in 186 requests on a phone: images 17.2 MB (64), scripts 2.1 MB (69) and HTML 200 KiB (1). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 14.8 MB together. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (1.7 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.
14 images below the first screen load straight away
14 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
42 KiB4 images are downloaded at several times the size a phone draws them, for example sc-Bars1.png at 580 px wide, shown at 187 px. Resized copies would save about 42 KiB.
About 5.6 g of CO₂ per visit
5.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.60 g of CO₂e: 672.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 68 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
70 internal links, 135 external
The homepage links to 70 pages on perfectketo.com and 135 external pages.
8 checks passed
Meta description: 99 characters
Your meta description is 99 characters: “Your Keto Journey Made Simple. Powerful products to help you stay energized, focused, and on track.”.
One H1 headline
Your main headline reads: “Early Black Friday Sale: Up to 45% Off!”.
Title: 51 characters
Your title is a healthy 51 characters: “Perfect Keto - Doctor-developed. Backed by science.”.
Canonical URL set
The canonical URL is https://perfectketo.com/.
Structured data in place
Structured data found: ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://perfectketo.com/sitemap_index.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,009 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://perfectketo.com/llms.txt (49 KiB, 192 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://perfectketo.com/collections/all-perfect-keto-products, which answers with an error. Visitors hit a dead end and search engines drop it.
2 linked pages hidden from search
https://perfectketo.com/tag/collagen and https://perfectketo.com/tag/exogenous-ketones are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://perfectketo.com/keto-recipes and https://perfectketo.com/recipes all use the title “400+ Keto Recipes - Perfect Keto”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://perfectketo.com/mission, https://perfectketo.com/blog, https://perfectketo.com/keto-kickstart, https://perfectketo.com/tag/collagen and https://perfectketo.com/tag/exogenous-ketones have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://perfectketo.com/keto-recipes and https://perfectketo.com/recipes use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://perfectketo.com/guide/the-ketogenic-diet, whose canonical is https://perfectketo.com/what-is-the-keto-diet. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://perfectketo.com/mission and https://perfectketo.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
1 checks passed
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
31 small tap targets
31 of 65 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'querySelectorAll')”.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 786 words of copy
The homepage carries about 786 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
21 calls to action
The homepage has 21 calls to action, for example “SHOP NOW”, “How to Start Keto” and “Join the Newsletter”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks, 3 trust badges and “5,979+ Reviews”.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies (measured from a US location before any click).
No consent tool detected
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.
44 other companies contacted
Loading the homepage contacts 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at perfectketo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Headquarters
- Austin
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on perfectketo.com, including 19 speed issues and 1 SEO issue. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.