Website review, no card needed
coasterfurniture.com website review
Visit site (opens in a new tab)Reviewed 20 November 202652 issues · 89 checks
This review found 52 issues worth fixing on coasterfurniture.com, 21 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.7 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.5 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.5 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.2 s |
| Oct 31, 2026 | 4.0 s |
| Nov 7, 2026 | 3.8 s |
| Nov 14, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 101 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 103 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 118 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 131 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 131 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 130 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 135 ms |
| Sep 19, 2026 | 134 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 131 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 129 ms |
| Nov 7, 2026 | 121 ms |
| Nov 14, 2026 | 121 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.4 s
2.7 s
4.1 s
5.5 s
6.8 s
8.2 s
9.6 s
10.9 s
Speed
Use efficient cache lifetimes
163.1 s · 55.5 MB307 files are served with short cache lifetimes, so returning visitors download them again (55.5 MB).
Reduce unused JavaScript
129.1 s · 23.5 MBAbout 23.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 129.1 s faster on a phone.
Improve image delivery
19.1 s · 13.2 MB20 images could be 13.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 19.1 s faster on a phone.
aftermkt.com adds 1.0 s
1.0 saftermkt.com costs a phone 1.0 s of main-thread work and 30.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
2.5 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Font display
1.2 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.2 s).
Mobile performance score: 24
24/100Your mobile performance score is 24. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.1 s
A phone's processor spends 9.1 s on main-thread work while loading, 4.5 s 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 (aftermkt.com, matterport.com and Google Tag Manager and others), adding 39.5 MB and 3.3 s of main-thread time.
matterport.com adds 970 ms
970 msmatterport.com costs a phone 970 ms of main-thread work and 6.3 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
890 ms · 368 KiBAbout 368 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 890 ms faster on a phone.
Google Tag Manager adds 866 ms
866 msGoogle Tag Manager costs a phone 866 ms of main-thread work and 1.6 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.
YouTube adds 401 ms
401 msYouTube costs a phone 401 ms of main-thread work and 1,003 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 466 ms. During a long task the page ignores taps.
2,008 HTML elements
The page has 2,008 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 52 KiB52 KiB could be saved by minifying CSS.
Minify JavaScript
89 KiB89 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.
1 checks passed
Server response: 39 ms
39 msYour server sent the HTML in 39 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: 245.7 s
245.7 sYour largest element takes 245.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “...”.
Speed Index: 23.5 s
23.5 sVisually, the page fills in at 23.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 307.9 s
307.9 sThe page becomes fully interactive after 307.9 s. Good is under 3.8 s.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
59 images without width and height
59 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.182
0.182The layout shifts by 0.182 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 104 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 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 FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.6 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 67.5 MB in 440 requests
67.5 MBYour homepage downloads 67.5 MB in 440 requests on a phone: scripts 34.8 MB (238), images 27.0 MB (50) and other files 4.1 MB (91). Under 2 MB keeps phones on slow connections fast.
26 images over 500 KB
26 images weigh 22.6 MB together. On a phone connection a single image that size takes seconds.
27 images far larger than shown
18.7 MB27 images are downloaded at several times the size a phone draws them, for example 907538_02xHD.jpg at 2,500 px wide, shown at 294 px. Resized copies would save about 18.7 MB.
32 images in older formats
32 images (24.8 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.
22 images below the first screen load straight away
22 images further down the page (16.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 19.1 g of CO₂ per visit
19.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 19.13 g of CO₂e: 2295.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (24 characters)
Your title is only 24 characters: “Coaster Furniture - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://coasterfurniture.com/sitemap.xml, so Google discovers your pages only by following links.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
253 internal links, 6 external
The homepage links to 253 pages on coasterfurniture.com and 6 external pages.
1 checks passed
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://coasterfurniture.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.
2 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 (1,633 words), so crawlers that don't run JavaScript still read it.
Other pages
7 linked pages are broken
Your homepage links to https://coasterfurniture.com/furniture/shopall, https://coasterfurniture.com/furniture/newarrivals, https://coasterfurniture.com/furniture/category/Bedroom-Sets, https://coasterfurniture.com/furniture/category/Beds, https://coasterfurniture.com/furniture/category/Headboards and https://coasterfurniture.com/furniture/category/Daybeds and 1 other, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages share a title
/ and https://coasterfurniture.com/Home/Index all use the title “Coaster Furniture - Home”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://coasterfurniture.com/browse/catalogs, https://coasterfurniture.com/news, https://coasterfurniture.com/blogs, https://coasterfurniture.com/become-a-dealer, https://coasterfurniture.com/customer-support and https://coasterfurniture.com/Home/Index and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://coasterfurniture.com/Home/Index, https://coasterfurniture.com/DealerLocator/DealerLocation and https://coasterfurniture.com/furniture/collections 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 99 found) and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://lh7-rt.googleusercontent.com/docsz/AD_4nXcWHR_y9wsY7ZaY8e8ogyZ2H1kXTFKAE8DY5XntD99Xf-R3WtfJxKmDDTl2CNN44lRmYk35M8BI8xHDze2Pqv-4Ne1qS50ZflkMXgImu9_rbiF7axYuXTuDcP_lQJfNft-N5VqF1A?key=3yggqe-qVT.
6 third-party cookies
6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameSite”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
92 of 111 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 468 words of copy
The homepage carries about 468 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: “Contact” and “Where To Buy”.
11 calls to action
The homepage has 11 calls to action, for example “Where To Buy”, “Shop All” and “Contact”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
21 other companies contacted
Loading the homepage contacts 21 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 coasterfurniture.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on coasterfurniture.com, including 26 speed issues, 8 SEO issues 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.