Website review, no card needed
clothandpaper.com website review
Visit site (opens in a new tab)Reviewed 5 November 202638 issues · 86 checks
This review found 38 issues worth fixing on clothandpaper.com, 12 of them high impact, across 86 checks. The most urgent: page weight: 26.7 MB in 519 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
74C- #86,971 of 124,581 reviewed websitesbeats 26%
- #54,619 of 69,967 online storesbeats 18%
- #51,296 of 63,604 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 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.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 145 ms |
| May 23, 2026 | 144 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 157 ms |
| Jul 18, 2026 | 159 ms |
| Jul 25, 2026 | 155 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 155 ms |
| Aug 15, 2026 | 156 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 160 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 158 ms |
| Oct 3, 2026 | 156 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 152 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 146 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
1.5 s
3.1 s
4.6 s
6.1 s
7.6 s
9.2 s
10.7 s
12.2 s
Speed
Render-blocking requests
1.6 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.9 s
A phone's processor spends 8.9 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,957 HTML elements
The page has 4,957 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
890 ms · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 890 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and route.com and others), adding 4.3 MB and 2.2 s of main-thread time.
Use efficient cache lifetimes
1.4 MB20 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Improve image delivery
50 ms · 1.3 MB30 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Google Tag Manager adds 454 ms
454 msGoogle Tag Manager costs a phone 454 ms of main-thread work and 822 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.
route.com adds 387 ms
387 msroute.com costs a phone 387 ms of main-thread work and 1.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.
Shopify adds 396 ms
396 msShopify costs a phone 396 ms of main-thread work and 990 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.
Duplicated JavaScript
485 KiB485 KiB JavaScript is shipped twice across bundles.
Klaviyo adds 290 ms
290 msKlaviyo costs a phone 290 ms of main-thread work and 615 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 318 ms. During a long task the page ignores taps.
Osano CMP adds 287 ms
287 msOsano CMP costs a phone 287 ms of main-thread work and 84 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.
Reduce unused CSS
150 ms · 145 KiBAbout 145 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
130 ms · 93 KiB93 KiB could be saved by minifying JavaScript.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify CSS
130 ms · 15 KiB15 KiB could be saved by minifying CSS.
Legacy JavaScript
57 KiBPolyfills for old browsers add 57 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: 15 ms
15 msYour server sent the HTML in 15 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: 10.2 s
10.2 sYour largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A video showcasing the Cloth & Paper collection — hands gli…”.
Speed Index: 16.8 s
16.8 sVisually, the page fills in at 16.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 42.4 s
42.4 sThe page becomes fully interactive after 42.4 s. Good is under 3.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
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 FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 145 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 512 ms
512 msReal visitors wait 512 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 26.7 MB in 519 requests
26.7 MBYour homepage downloads 26.7 MB in 519 requests on a phone: media 17.8 MB (2), scripts 4.2 MB (141) and images 2.3 MB (49). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (116 KiB) is 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 7.6 g of CO₂ per visit
7.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.57 g of CO₂e: 907.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
252 internal links, 15 external
The homepage links to 252 pages on clothandpaper.com and 15 external pages.
7 checks passed
One H1 headline
Your main headline reads: “CLOTH & PAPER”.
Title: 62 characters
Your title is a healthy 62 characters: “CLOTH & PAPER - LUXURY AESTHETIC PLANNERS, DIVIDERS, & INSERTS”.
Canonical URL set
The canonical URL is https://www.clothandpaper.com/.
Structured data in place
Structured data found: BreadcrumbList, 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.clothandpaper.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,978 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.clothandpaper.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://www.clothandpaper.com/collections/subscriber-exclusive is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.clothandpaper.com/boutiq has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.clothandpaper.com/boutiq, whose canonical is https://www.clothandpaper.com/apps/video/vs/calllink/38ed1131-013f-402e-a5da-6a126abd27da. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.clothandpaper.com/pages/rewards, https://www.clothandpaper.com/pages/planner-size-guide, https://www.clothandpaper.com/boutiq and https://www.clothandpaper.com/collections/best-sellers have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.clothandpaper.com/boutiq took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 106 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 broken image
1 image failed to load on a phone, for example https://www.clothandpaper.com/.
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.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.
2 checks passed
Tap targets are thumb-sized
30 of 37 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 670 words of copy
The homepage carries about 670 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: “START PLANNING”.
21 calls to action
The homepage has 21 calls to action, for example “Shop All”, “Get Started” and “SHOP”.
18 short forms
18 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
33 other companies contacted
Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) loads with the page.
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 clothandpaper.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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Product Filters Search · Blocky Fraud Blocker · Klaviyo Email Marketing Sms · Warnify Pro Warnings · Yotpo Loyalty Rewards · Triplewhale · Route Protection Tracking · Microsoft Clarity · Yotpo Product Reviews · Product Warnings · Simple Bundle · Accessibly App · Swym Wishlist Plus · Freegifts · rechargecdn.com · electricsms.com · cloudfront.net · rebuyengine.com · boutiq.app
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 | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Henrico
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on clothandpaper.com, including 23 speed issues, 1 SEO issue and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.