Website review, no card needed

fastfood.com logo

fastfood.com website review

Visit site (opens in a new tab)Reviewed 4 November 202628 issues · 75 checks

This review found 28 issues worth fixing on fastfood.com, 8 of them high impact, across 75 checks. The most urgent: main-thread work: 5.1 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of fastfood.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fastfood.com at 0.4 s0.4 s
  2. fastfood.com at 0.8 s0.8 s
  3. fastfood.com at 1.1 s1.1 s
  4. fastfood.com at 1.5 s1.5 s
  5. fastfood.com at 1.9 s1.9 s
  6. fastfood.com at 2.3 s2.3 s
  7. fastfood.com at 2.6 s2.6 s
  8. fastfood.com at 3.0 s3.0 s

Speed

10 to fix68
  • Main-thread work: 5.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (FullStory, Yotpo and replocdn.com and others), adding 1.6 MB and 1.3 s of main-thread time.

  • Mobile performance score: 68

    68/100

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

  • Use efficient cache lifetimes

    250 ms · 469 KiB

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

  • Render-blocking requests

    700 ms

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

  • Reduce unused JavaScript

    459 KiB

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

  • FullStory adds 349 ms

    349 ms

    FullStory costs a phone 349 ms of main-thread work and 169 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 adds 265 ms

    265 ms

    Yotpo costs a phone 265 ms of main-thread work and 272 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 adds 221 ms

    221 ms

    Shopify costs a phone 221 ms of main-thread work and 702 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.

  • 11 long tasks on the main thread

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

  • Improve image delivery

    69 KiB

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

  • Reduce unused CSS

    59 KiB

    About 59 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    23 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Minify CSS

    15 KiB

    15 KiB could be saved by minifying CSS.

  • 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: 16 ms

    16 ms

    Your server sent the HTML in 16 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix63
  • Time to Interactive: 15.2 s

    15.2 s

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

  • Largest Contentful Paint: 4.3 s

    4.3 s

    Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A shirtless man drinks water from a bottle in a sunny outdo…”.

  • Total Blocking Time: 653 ms

    653 ms

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

  • Speed Index: 3.5 s

    3.5 s

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 310 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 310 requests on a phone: scripts 1.5 MB (132), other files 886 KiB (136) and images 483 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (253 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.

  • 3 images below the first screen load straight away

    3 images further down the page (176 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8793
  • 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.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 5 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8586
  • Title is short (27 characters)

    Your title is only 27 characters: “Performance Fuel - Fastfood”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • One H1 headline

    Your <h1> is empty.

  • 36 internal links, 5 external

    The homepage links to 36 pages on fastfood.com and 5 external pages.

6 checks passed
  • Meta description: 77 characters

    Your meta description is 77 characters: “Performance fuel formulated to keep you running- with real food and no crash.”.

  • Canonical URL set

    The canonical URL is https://fastfood.com/.

  • Structured data in place

    Structured data found: Organization 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://fastfood.com/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (592 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://fastfood.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 6 pages without a meta description

    https://fastfood.com/collections/all-products, https://fastfood.com/pages/how-to-fuel, https://fastfood.com/pages/our-story, https://fastfood.com/pages/contact-us, https://fastfood.com/blogs/news and https://fastfood.com/collections/merch have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://fastfood.com/collections/all-products, https://fastfood.com/pages/how-to-fuel, https://fastfood.com/pages/our-story, https://fastfood.com/collections/gels, https://fastfood.com/collections/gummies and https://fastfood.com/collections/merch have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://fastfood.com/blogs/news 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.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://wiser.expertvillagemedia.com/cart_drawer_admin/getCartData?shop=lovefastfood.mysho…”.

2 checks passed
  • Tap targets are thumb-sized

    6 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No risk reducer

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

  • About 542 words of copy

    The homepage carries about 542 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Shop”, “Contact” and “SHOP NOW”.

  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads FullStory, Google Ads, 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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 29 other companies contacted

    Loading the homepage contacts 29 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 fastfood.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager | FullStory
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on fastfood.com, including 14 speed issues, 3 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25