Website review, no card needed
decorium.com website review
Visit site (opens in a new tab)Reviewed 21 November 202646 issues · 95 checks
This review found 46 issues worth fixing on decorium.com, 18 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. 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
71C- #101,320 of 125,870 reviewed websitesbeats 17%
- #61,553 of 70,289 online storesbeats 10%
- #57,050 of 63,840 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 89 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 82 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 89 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 91 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 90 ms |
| Aug 15, 2026 | 88 ms |
| Aug 22, 2026 | 90 ms |
| Aug 29, 2026 | 91 ms |
| Sep 5, 2026 | 91 ms |
| Sep 12, 2026 | 89 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 89 ms |
| Oct 10, 2026 | 88 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 89 ms |
| Oct 31, 2026 | 88 ms |
| Nov 7, 2026 | 94 ms |
| Nov 14, 2026 | 94 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
Speed
Reduce unused JavaScript
7.0 s · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.
Use efficient cache lifetimes
7.2 s · 1.5 MB33 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Reduce unused CSS
1.3 s · 334 KiBAbout 334 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Render-blocking requests
1.6 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 4.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,985 HTML elements
The page has 3,985 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 (Google Tag Manager, nowinstore.com and YouTube and others), adding 3.8 MB and 2.6 s of main-thread time.
nowinstore.com adds 605 ms
605 msnowinstore.com costs a phone 605 ms of main-thread work and 1.2 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.
Google Tag Manager adds 649 ms
649 msGoogle Tag Manager costs a phone 649 ms of main-thread work and 540 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.
YouTube adds 556 ms
556 msYouTube costs a phone 556 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 570 ms. During a long task the page ignores taps.
Google CDN adds 181 ms
181 msGoogle CDN costs a phone 181 ms of main-thread work and 407 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.
LiveChat adds 122 ms
122 msLiveChat costs a phone 122 ms of main-thread work and 363 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 KiB4 images could be 250 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Duplicated JavaScript
150 ms · 59 KiB59 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 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: 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: 22.7 s
22.7 sYour largest element takes 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 36.4 s
36.4 sThe page becomes fully interactive after 36.4 s. Good is under 3.8 s.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.20
0.20For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.17
0.17The layout shifts by 0.17 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 89 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 99 ms
99 msReal visitors wait 99 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 594 ms
594 msReal visitors wait 594 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 10.6 MB in 292 requests
10.6 MBYour homepage downloads 10.6 MB in 292 requests on a phone: scripts 4.2 MB (99), media 4.1 MB (2) and other files 954 KiB (139). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
201 KiB1 image is downloaded at several times the size a phone draws it, for example trust-badge.png at 2,303 px wide, shown at 90 px. Resized copies would save about 201 KiB.
1 image below the first screen load straight away
1 image further down the page (204 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.0 g of CO₂ per visit
3.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.01 g of CO₂e: 361.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
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 15 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 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“” and “Take advantage of our FREE interior design servic…”). One clear main headline is easier for people and search engines.
Meta description is long (166 characters)
Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
119 internal links, 6 external
The homepage links to 119 pages on decorium.com and 6 external pages.
5 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “Decorium | Furniture, Home Décor & Interior Design | Toronto”.
Canonical URL set
The canonical URL is https://decorium.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://decorium.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.
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,407 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://decorium.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://decorium.com/collections/stressless-gallery has no meta description, so Google writes the search snippet from whatever text it finds.
12 pages share a meta description
https://decorium.com/collections/living-room, https://decorium.com/collections/sofas, https://decorium.com/collections/sectionals-large-living, https://decorium.com/collections/sofa-beds, https://decorium.com/collections/accent-chairs and https://decorium.com/collections/fabric-leather-recliner and 6 others use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://decorium.com/about, whose canonical is https://decorium.com/pages/about. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://decorium.com/contact 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 73 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.
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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355029661&tm=gtm002&Ver=2&mid=efe219d7-13af-4877-b15f-be1bc7c7f399&bo=1&sid=8ccfaf40e5d711f1807ced78f22dcd72&vid=8ccfdee0e5d711f1829f611fad247c9d&vids=1&msclkid=N>m_.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
42 of 44 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 532 words of copy
The homepage carries about 532 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LOGIN / REGISTER” and “Book your appointment”.
10 calls to action
The homepage has 10 calls to action, for example “Contact Us”, “Login/Register” and “Sign up!”.
6 short forms
6 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks, a star rating and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 3 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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 3 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.
52 other companies contacted
Loading the homepage contacts 52 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 decorium.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Powerful Form Builder · Froonze Loyalty Wishlist · Sticky Cart By Qikify · squadkin.com · revampco.com · cloudfront.net
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Toronto
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on decorium.com, including 23 speed issues, 4 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.