potatocorner.com website review

9 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.0 s faster on a phone.

71 files are served with short cache lifetimes, so returning visitors download them again (3.1 MB).

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

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

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

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

About 77 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

1 third-party service load with your homepage (Google CDN), adding 31 KiB and 103 ms of main-thread time.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying CSS.

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 see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

Real visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Chicken Fries - Website Banner copy”.

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 74 requests on a phone: images 4.0 MB (10), scripts 279 KiB (27) and stylesheets 256 KiB (31). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example SURFRIES-KV-1-LED-Horizontal-copy.jpg at 1,920 px wide, shown at 370 px. Resized copies would save about 1.5 MB.

8 images (3.8 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 1.32 g of CO₂e: 158.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

13 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: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

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

There are 2 <h1> headlines (“JOIN OUR FAMILY” and “SHAKE UP”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://potatocorner.com/wp-sitemap.xml, so Google discovers your pages only by following links.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 19 pages on potatocorner.com and 5 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 /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.

Your homepage links to /shaking-soon, which answers with an error. Visitors hit a dead end and search engines drop it.

/franchising and /uncategorized/crave-the-fave-flavor-every-moment-with-the-ultimate-snack-experience/,https://potatocorner.com/whats-shaking/experience-snacks-worth-every-bite-/,%20%20https://potatocorner.com/whats-shaking/summer-pocollectibles-have-arrived-/,%20https://potatocorner.com/events/,%20https://potatocorner.com/franchising/, all use the title “Franchising – Potato Corner”. Search engines can't tell which page to show for a search, so each competes with the others.

/history, /extended-partners, /countries-and-territories, /franchising, /events and /menu and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /uncategorized/crave-the-fave-flavor-every-moment-with-the-ultimate-snack-experience/,https://potatocorner.com/whats-shaking/experience-snacks-worth-every-bite-/,%20%20https://potatocorner.com/whats-shaking/summer-pocollectibles-have-arrived-/,%20https://potatocorner.com/events/,%20https://potatocorner.com/franchising/,, whose canonical is /franchising. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/countries-and-territories, /franchising, /events, /menu, /store-locator and /uncategorized/crave-the-fave-flavor-every-moment-with-the-ultimate-snack-experience/,https://potatocorner.com/whats-shaking/experience-snacks-worth-every-bite-/,%20%20https://potatocorner.com/whats-shaking/summer-pocollectibles-have-arrived-/,%20https://potatocorner.com/events/,%20https://potatocorner.com/franchising/, have no <h1> headline, so visitors and search engines get no clear main topic.

/extended-partners, /countries-and-territories, /franchising, /events, /menu and /store-locator and 2 others have 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.

/franchising and /uncategorized/crave-the-fave-flavor-every-moment-with-the-ultimate-snack-experience/,https://potatocorner.com/whats-shaking/experience-snacks-worth-every-bite-/,%20%20https://potatocorner.com/whats-shaking/summer-pocollectibles-have-arrived-/,%20https://potatocorner.com/events/,%20https://potatocorner.com/franchising/, took over 3 s to send their HTML from our server.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

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

1 link from your homepage to your own site is broken, for example https://potatocorner.com/shaking-soon/ (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://potatocorner.com/uncategorized/crave-the-fave-flavor-every-moment-with-the-ultimate-snack-experience/,https://potatocorner.com/whats-shaking/experience-snacks-worth-every-bite-/,%20%20https://potatocorner.com/whats-shaking/summer-pocollectibles-have-arrived-/,%20https://potatocorner.com/events/,%20https://potatocorner.com/franchising/,.

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

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

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

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

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage has only about 87 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be potatocorner.com is still delivered. Reports are on, so moving to quarantine is the next step.

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.

Opening the homepage sets 2 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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.