Website review, no card needed

uprightoats.com logo

uprightoats.com website review

Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 76 checks

This review found 32 issues worth fixing on uprightoats.com, 9 of them high impact, across 76 checks. The most urgent: improve image delivery. 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 uprightoats.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. uprightoats.com at 0.7 s0.7 s
  2. uprightoats.com at 1.3 s1.3 s
  3. uprightoats.com at 2.0 s2.0 s
  4. uprightoats.com at 2.6 s2.6 s
  5. uprightoats.com at 3.3 s3.3 s
  6. uprightoats.com at 4.0 s4.0 s
  7. uprightoats.com at 4.6 s4.6 s
  8. uprightoats.com at 5.3 s5.3 s

Speed

5 to fix62
  • Improve image delivery

    2.8 s · 804 KiB

    11 images could be 804 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.

  • Reduce unused JavaScript

    900 ms · 158 KiB

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

  • Mobile performance score: 62

    62/100

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

  • Reduce unused CSS

    300 ms · 80 KiB

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

  • Shopify adds 55 ms

    55 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Shopify and Secomapp and others), adding 691 KiB and 259 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 38 KiB

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

  • Legacy JavaScript

    150 ms · 11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 132 ms. During a long task the page ignores taps.

  • Render-blocking requests

    50 ms

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

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 16.5 s

    16.5 s

    Your largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Oatmilk, but better High-protein instant oatmilk - just add…”.

  • Time to Interactive: 16.9 s

    16.9 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • 15 images without width and height

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

  • 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
  • Total Blocking Time: 82 ms

    82 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.7 MB in 256 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 256 requests on a phone: images 2.0 MB (25), other files 764 KiB (98) and scripts 673 KiB (111). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    402 KiB

    2 images are downloaded at several times the size a phone draws them, for example sparkle.png at 2,500 px wide, shown at 440 px. Resized copies would save about 402 KiB.

  • 2 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.05 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8992
  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (3 elements)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 3 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 21 images without alt text

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

  • All page content should be contained by landmarks (1 element)

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • 5 H1 headlines

    There are 5 <h1> headlines (“Oat protein”, “Prebiotic fiber” and “Vitamins A, B12, and D”). One clear main headline is easier for people and search engines.

  • Meta description is long (316 characters)

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

  • 26 internal links, 5 external

    The homepage links to 26 pages on uprightoats.com and 5 external pages.

6 checks passed
  • Title: 55 characters

    Your title is a healthy 55 characters: “Upright: high-protein instant oatmilk - just add water!”.

  • Canonical URL set

    The canonical URL is https://www.uprightoats.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://www.uprightoats.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://www.uprightoats.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix67
  • 1 page without a title

    https://www.uprightoats.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.uprightoats.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 7 pages without a meta description

    https://www.uprightoats.com/pages/ingredients, https://www.uprightoats.com/pages/about, https://www.uprightoats.com/blogs/news, https://www.uprightoats.com/customer_authentication/redirect, https://www.uprightoats.com/policies/refund-policy and https://www.uprightoats.com/policies/terms-of-service and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.uprightoats.com/products/instant-oatmilk-vanilla and https://www.uprightoats.com/products/instant-oatmilk-chocolate use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.uprightoats.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 internal pages checked

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

3 checks passed
  • Linked pages load

    All 14 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.

Best practices

3 to fixGoogle 7785
  • 3 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Error from API: undefined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

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

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 481 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop”, “Contact” and “Shop now”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks and a star rating.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 1 more (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.

  • 14 cookies set on arrival

    14

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

  • 27 other companies contacted

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

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · chimpstatic.com · nfcube.com · secomapp.com · stamped.io

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

  • The footer still says © 2023.

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
New Haven

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on uprightoats.com, including 10 speed issues, 2 SEO issues and 4 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