Website review, no card needed
revolutionfabricsbytheyard.com website review
Visit site (opens in a new tab)Reviewed 11 November 202636 issues · 82 checks
This review found 36 issues worth fixing on revolutionfabricsbytheyard.com, 11 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
78C- #63,225 of 126,508 reviewed websitesbeats 45%
- #40,919 of 70,497 online storesbeats 36%
- #39,034 of 63,990 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 145 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 158 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 172 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 156 ms |
| Aug 1, 2026 | 156 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 157 ms |
| Aug 22, 2026 | 158 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 158 ms |
| Sep 12, 2026 | 156 ms |
| Sep 19, 2026 | 160 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 162 ms |
| Nov 7, 2026 | 162 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.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.0 s
3.5 s
Speed
Improve image delivery
10.8 s · 4.6 MB16 images could be 4.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.8 s faster on a phone.
Reduce unused JavaScript
2.0 s · 384 KiBAbout 384 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Yotpo and Clarity and others), adding 5.7 MB and 456 ms of main-thread time.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 175 KiB14 files are served with short cache lifetimes, so returning visitors download them again (175 KiB).
Shopify adds 145 ms
145 msShopify costs a phone 145 ms of main-thread work and 5.1 MB 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.
Reduce unused CSS
450 ms · 79 KiBAbout 79 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 504 ms. During a long task the page ignores taps.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
350 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Minify JavaScript
150 ms · 11 KiB11 KiB could be saved by minifying JavaScript.
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 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.
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 40.5 s
40.5 sYour largest element takes 40.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Revolution Jasper performance upholstery fabric on a sofa w…”.
Speed Index: 19.9 s
19.9 sVisually, the page fills in at 19.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 41.7 s
41.7 sThe page becomes fully interactive after 41.7 s. Good is under 3.8 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 854 ms
854 msReal visitors wait 854 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 242 ms
242 msScripts block taps and scrolling for 242 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 145 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 190 ms
190 msReal visitors wait 190 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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 10.1 MB in 344 requests
10.1 MBYour homepage downloads 10.1 MB in 344 requests on a phone: images 7.0 MB (39), scripts 1.9 MB (157) and other files 708 KiB (116). Under 2 MB keeps phones on slow connections fast.
16 images far larger than shown
5.2 MB16 images are downloaded at several times the size a phone draws them, for example jasper_345867_23e1_2.png at 2,755 px wide, shown at 370 px. Resized copies would save about 5.2 MB.
3 images over 500 KB
3 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.
21 images below the first screen load straight away
21 images further down the page (5.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
7 images in older formats
7 images (2.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.
About 2.9 g of CO₂ per visit
2.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.88 g of CO₂e: 345.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
9 links inside paragraphs rely on colour alone to stand out.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
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
Meta description is long (305 characters)
Your meta description is 305 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Brand, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.
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.
117 internal links, 25 external
The homepage links to 117 pages on revolutionfabricsbytheyard.com and 25 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Performance Fabrics Built to last.”.
Title: 47 characters
Your title is a healthy 47 characters: “The Best Upholstery Fabric — Revolution Fabrics”.
Canonical URL set
The canonical URL is https://revolutionfabrics.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://revolutionfabrics.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://revolutionfabrics.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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (916 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without an H1
https://revolutionfabrics.com/collections/designer-curated-collections and https://revolutionfabrics.com/pages/who-we-are have 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 46 found) and read each the way a search engine does.
6 checks passed
Linked pages load
9 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.
Every page has a meta description
All 9 pages that loaded have a meta description.
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 9 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_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
17 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 674 words of copy
The homepage carries about 674 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP FABRIC” and “APPLY FOR A TRADE ACCOUNT”.
16 calls to action
The homepage has 16 calls to action, for example “Wholesale sign up form”, “How to Order” and “Shop Fabric”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 22 testimonial or review blocks and 18 customer or partner logos.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
36 other companies contacted
Loading the homepage contacts 36 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 revolutionfabricsbytheyard.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Yotpo Loyalty Rewards · Yotpo Product Reviews · Blocky Fraud Blocker · Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · Forms · aaawebstore.com · automizely.com
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
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on revolutionfabricsbytheyard.com, including 19 speed issues and 3 SEO issues. 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.