Website review, no card needed
allsumhome.com website review
Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 78 checks
This review found 38 issues worth fixing on allsumhome.com, 12 of them high impact, across 78 checks. The most urgent: render-blocking 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- #87,749 of 125,791 reviewed websitesbeats 26%
- #54,827 of 70,264 online storesbeats 18%
- #51,469 of 63,827 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 148 ms |
| May 23, 2026 | 151 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 170 ms |
| Aug 15, 2026 | 178 ms |
| Aug 22, 2026 | 182 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 195 ms |
| Sep 12, 2026 | 197 ms |
| Sep 19, 2026 | 194 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 196 ms |
| Oct 10, 2026 | 195 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 205 ms |
| Oct 31, 2026 | 202 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.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.9 s
9.2 s
10.5 s
Speed
Render-blocking requests
1.2 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 8.6 s
A phone's processor spends 8.6 s on main-thread work while loading, 4.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,413 HTML elements
The page has 4,413 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, PayPal and Facebook and others), adding 3.4 MB and 2.0 s of main-thread time.
Reduce unused JavaScript
450 ms · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
1.0 MB39 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Shopify adds 719 ms
719 msShopify costs a phone 719 ms of main-thread work and 1.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.
PayPal adds 490 ms
490 msPayPal costs a phone 490 ms of main-thread work and 967 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.
Improve image delivery
250 ms · 324 KiB12 images could be 324 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Google CDN adds 134 ms
134 msGoogle CDN costs a phone 134 ms of main-thread work and 299 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.
chatty.net adds 50 ms
50 mschatty.net costs a phone 50 ms of main-thread work and 333 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 225 ms. During a long task the page ignores taps.
Legacy JavaScript
79 KiBPolyfills for old browsers add 79 KiB JavaScript that modern phones do not need.
Reduce unused CSS
64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 35 ms
35 msYour server sent the HTML in 35 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.
Time to Interactive: 36.2 s
36.2 sThe page becomes fully interactive after 36.2 s. Good is under 3.8 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 788 ms
788 msScripts block taps and scrolling for 788 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 202 ms
202 msReal visitors wait 202 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 148 ms to 202 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 597 ms
597 msReal visitors wait 597 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 477 requests
6.3 MBYour homepage downloads 6.3 MB in 477 requests on a phone: scripts 3.0 MB (150), other files 1.2 MB (194) and images 1.1 MB (62). Under 2 MB keeps phones on slow connections fast.
About 1.8 g of CO₂ per visit
1.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 214.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Inline text spacing must be adjustable with custom stylesheets (1 element)
Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.
10 images without alt text
10 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.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
1 checks passed
12 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 14 WCAG 2.2 A/AA and best-practice rules on the phone render: 12 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “LED Medicine Cabinets, Bathroom Mirrors & Shower Doors | Allsumhome”.
Meta description is long (238 characters)
Your meta description is 238 characters; Google truncates after about 160, so the end of your pitch is cut.
No robots.txt
There is no robots.txt at allsumhome.com/robots.txt, the first file search crawlers ask for.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
336 internal links, 13 external
The homepage links to 336 pages on allsumhome.com and 13 external pages.
5 checks passed
One H1 headline
Your main headline reads: “LED Medicine Cabinets, Lighted Bathroom Mirrors and Shower Doors”.
Canonical URL set
The canonical URL is https://www.allsumhome.com/.
Structured data in place
Structured data found: WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://www.allsumhome.com/sitemap.xml.
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://www.allsumhome.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.
Other pages
3 pages without a meta description
https://www.allsumhome.com/collections/all, https://www.allsumhome.com/collections/new-arrivals and https://www.allsumhome.com/collections/caivell have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://www.allsumhome.com/collections/all, https://www.allsumhome.com/policies/shipping-policy, https://www.allsumhome.com/pages/shipment-and-delivery, https://www.allsumhome.com/collections/new-arrivals, https://www.allsumhome.com/collections/solen and https://www.allsumhome.com/collections/caivell 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 138 found) and read each the way a search engine does.
5 checks passed
Linked pages load
6 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.
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 6 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “[Reach Pixel] failed to POST event: TypeError: Failed to fetch”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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.
Only about 18 words
The homepage has only about 18 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
26 calls to action
The homepage has 26 calls to action, for example “APPLY”, “New Arrivals | Learn More” and “Shop By Size”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 5 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 6 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.
31 cookies set on arrival
31Opening the homepage sets 31 cookies, 4 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.
49 other companies contacted
Loading the homepage contacts 49 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 allsumhome.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 22 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Sa Variants · Indexgpt · Ta Mappy Store Locator Maps · Judge Me Reviews · Zigpoll Customer Surveys · Uppromote Affiliate · Bm Country Blocker Ip Blocker · Ymq Product Options · Boostymark Regionblock · Affliate By Secomapp · Product Ads By Criteo · Ymq Cart Drawer Cart Upsell · Avada Faqs · autoketing.org · archive-digger.com · cloudfront.net · hubapi.com · kaktusapp.com · b-cdn.net · rakutenadvertising.io · pictureit.co · kmalgo.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 38 issues on allsumhome.com, including 20 speed issues, 4 SEO issues and 3 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.