Website review, no card needed

upsidefoods.com logo

upsidefoods.com website review

Visit site (opens in a new tab)Reviewed 31 October 202631 issues · 73 checks

This review found 31 issues worth fixing on upsidefoods.com, 16 of them high impact, across 73 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
5.4 s1.2 sMay 9Oct 244.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.3 s
Aug 1, 20262.5 s
Aug 8, 20263.8 s
Aug 15, 20264.5 s
Aug 22, 20264.6 s
Aug 29, 20264.7 s
Sep 5, 20264.8 s
Sep 12, 20264.8 s
Sep 19, 20264.8 s
Sep 26, 20264.8 s
Oct 3, 20264.9 s
Oct 10, 20264.8 s
Oct 17, 20264.8 s
Oct 24, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
128 ms86 msMay 9Oct 24123 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202696 ms
May 16, 202697 ms
May 23, 2026101 ms
May 30, 202695 ms
Jun 6, 202695 ms
Jun 13, 202691 ms
Jun 20, 202691 ms
Jun 27, 202698 ms
Jul 4, 202698 ms
Jul 11, 202698 ms
Jul 18, 2026101 ms
Jul 25, 2026104 ms
Aug 1, 2026104 ms
Aug 8, 2026107 ms
Aug 15, 2026109 ms
Aug 22, 2026111 ms
Aug 29, 2026113 ms
Sep 5, 2026112 ms
Sep 12, 2026111 ms
Sep 19, 2026108 ms
Sep 26, 2026111 ms
Oct 3, 2026115 ms
Oct 10, 2026120 ms
Oct 17, 2026123 ms
Oct 24, 2026123 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

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

How it loaded on a phone

  1. upsidefoods.com at 0.6 s0.6 s
  2. upsidefoods.com at 1.2 s1.2 s
  3. upsidefoods.com at 1.7 s1.7 s
  4. upsidefoods.com at 2.3 s2.3 s
  5. upsidefoods.com at 2.9 s2.9 s
  6. upsidefoods.com at 3.5 s3.5 s
  7. upsidefoods.com at 4.1 s4.1 s
  8. upsidefoods.com at 4.7 s4.7 s

Speed

5 to fix65
  • Use efficient cache lifetimes

    9.2 s · 11.8 MB

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

  • Improve image delivery

    6.3 s · 11.4 MB

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

  • Reduce unused JavaScript

    1.2 s · 231 KiB

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

  • Mobile performance score: 65

    65/100

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

  • Google Tag Manager adds 205 ms

    205 ms

    Google Tag Manager costs a phone 205 ms of main-thread work and 340 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 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and Cloudflare and others), adding 581 KiB and 344 ms of main-thread time.

  • Reduce unused CSS

    120 ms · 13 KiB

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    23 KiB

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

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

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 437 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

8 to fix33
  • 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.

  • Real-user LCP: 5.7 s

    5.7 s

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

  • Real-user CLS: 0.99

    0.99

    For real visitors the layout shifts by 0.99 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 35.8 s

    35.8 s

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

  • Time to Interactive: 38.2 s

    38.2 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Tap response (INP) got 27% slower for real visitors

    +27%

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

  • Largest content (LCP) got 187% slower for real visitors

    +187%

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

6 checks passed
  • Real-user INP: 133 ms

    133 ms

    Real visitors wait 133 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 570 ms

    570 ms

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

  • Total Blocking Time: 158 ms

    158 ms

    Scripts block the page for only 158 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 12.4 MB in 67 requests

    12.4 MB

    Your homepage downloads 12.4 MB in 67 requests on a phone: images 11.5 MB (16), scripts 715 KiB (25) and fonts 148 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 9.7 MB together. On a phone connection a single image that size takes seconds.

  • 11 images far larger than shown

    8.2 MB

    11 images are downloaded at several times the size a phone draws them, for example 1ac7cd632617ab650161363e347b0bcc9cc88b5f.png at 2,182 px wide, shown at 342 px. Resized copies would save about 8.2 MB.

  • 12 images in older formats

    12 images (11.5 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.

  • 3 images below the first screen load straight away

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

  • About 3.5 g of CO₂ per visit

    3.52 g

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

Accessibility

2 to fixGoogle 9697
  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 17 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 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9277
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://upside2026.wpenginepowered.com)”.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at upsidefoods.com/robots.txt, the first file search crawlers ask for.

  • 1 link with vague text

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

  • 23 internal links, 7 external

    The homepage links to 23 pages on upsidefoods.com and 7 external pages.

4 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “Delicious meat grown from animal cells. No farm, no fowl. Discover UPSIDE Chicken: cultivated chicken that's kind to an…”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “UPSIDE Foods | Make Meat Right”.

  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

100
  • No llms.txt

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

3 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://upsidefoods.com/education has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://upsidefoods.com/newsletter and https://upsidefoods.com/epic-tour have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://upsidefoods.com/contact 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.

  • 10 internal pages checked

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

5 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • 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 10 pages that loaded have a <title>.

Best practices

Google 100100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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 direct contact details

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 990 words of copy

    The homepage carries about 990 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 4 cookies set on arrival

    4

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

  • 9 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

Company

Employees
151
Founded
2015
Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on upsidefoods.com, including 13 speed issues, 5 SEO issues and 3 conversion gaps. 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