Website review, no card needed
rebelcheese.com website review
Visit site (opens in a new tab)Reviewed 7 November 202618 issues · 78 checks
This review found 18 issues worth fixing on rebelcheese.com, 4 of them high impact, across 78 checks. The most urgent: page weight: 23.0 MB in 279 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
94A- #255 of 120,262 reviewed websitesbeats 100%
- #84 of 68,103 online storesbeats 100%
- #82 of 62,065 Shopify storesbeats 100%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 179 ms |
| May 23, 2026 | 195 ms |
| May 30, 2026 | 204 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 219 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 210 ms |
| Jul 4, 2026 | 206 ms |
| Jul 11, 2026 | 206 ms |
| Jul 18, 2026 | 209 ms |
| Jul 25, 2026 | 211 ms |
| Aug 1, 2026 | 213 ms |
| Aug 8, 2026 | 210 ms |
| Aug 15, 2026 | 206 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 200 ms |
| Sep 5, 2026 | 198 ms |
| Sep 12, 2026 | 197 ms |
| Sep 19, 2026 | 200 ms |
| Sep 26, 2026 | 203 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 204 ms |
| Oct 17, 2026 | 204 ms |
| Oct 24, 2026 | 204 ms |
| Oct 31, 2026 | 199 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Improve image delivery
348 KiB7 images could be 348 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,289 HTML elements
The page has 2,289 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 509 ms 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 (Shopify, videowise.com and shop.app and others), adding 452 KiB and 63 ms of main-thread time.
Reduce unused CSS
85 KiBAbout 85 KiB of CSS is downloaded but never applied on this page.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 66 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
63 KiB11 files are served with short cache lifetimes, so returning visitors download them again (63 KiB).
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
2 checks passed
Mobile performance score: 98
98/100Your mobile performance score is 98. That is in Google's “good” band (90 and up).
Server response: 22 ms
22 msYour server sent the HTML in 22 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 8.3 s
8.3 sThe page becomes fully interactive after 8.3 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 179 ms to 199 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 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 188 ms
188 msReal visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (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.
Real-user TTFB: 516 ms
516 msReal visitors wait 516 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.3 s
3.3 sVisually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.6 s
1.6 sYour largest element renders in 1.6 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “CHEESE WITHOUT COMPROMISE.”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 23.0 MB in 279 requests
23.0 MBYour homepage downloads 23.0 MB in 279 requests on a phone: media 20.5 MB (3), other files 782 KiB (96) and images 710 KiB (20). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (266 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 6.5 g of CO₂ per visit
6.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.52 g of CO₂e: 782.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
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 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 47 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Rebel Cheese” and “Cheese withoutcompromise.”). One clear main headline is easier for people and search engines.
Meta description is long (279 characters)
Your meta description is 279 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//rebelcheese.com/cdn/shop/files/rebel_cheese_simple_lo…”.
122 internal links, 5 external
The homepage links to 122 pages on rebelcheese.com and 5 external pages.
5 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Rebel Cheese | Award-Winning Artisanal Dairy-Free Cheese”.
Canonical URL set
The canonical URL is https://rebelcheese.com/.
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://rebelcheese.com/sitemap.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: 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,032 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://rebelcheese.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://rebelcheese.com/products/build-your-own-cheese-board is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://rebelcheese.com/policies/shipping-policy, https://rebelcheese.com/policies/refund-policy and https://rebelcheese.com/pages/reviews have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://rebelcheese.com/pages/reviews has 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 49 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
26 of 28 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 597 words of copy
The homepage carries about 597 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL”.
11 calls to action
The homepage has 11 calls to action, for example “FAQ & Contact Us”, “Shop” and “SHOP ALL”.
12 short forms
12 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and “10,000+ reviews”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call 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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies, 2 of them by other companies (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.
31 other companies contacted
Loading the homepage contacts 31 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 rebelcheese.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Redo · Klaviyo Email Marketing Sms · Videowise Connect · Gorgias Live Chat Helpdesk · Skio Subscriptions Yc S20 · Deco Labels Badges · Freegifts · 9gtb.com · bogos.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
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
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 18 issues on rebelcheese.com, including 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.