Website review, no card needed

adorracarpet.com logo

adorracarpet.com website review

Visit site (opens in a new tab)Reviewed 17 November 202641 issues · 85 checks

This review found 41 issues worth fixing on adorracarpet.com, 13 of them high impact, across 85 checks. The most urgent: avoid multiple page redirects. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.4 s2.6 sMay 30Nov 143.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.2 s
Jun 6, 20263.1 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.1 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.7 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.9 s
Nov 7, 20262.9 s
Nov 14, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
189 ms120 msMay 30Nov 14155 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026154 ms
Jun 6, 2026139 ms
Jun 13, 2026129 ms
Jun 20, 2026130 ms
Jun 27, 2026145 ms
Jul 4, 2026154 ms
Jul 11, 2026170 ms
Jul 18, 2026181 ms
Jul 25, 2026167 ms
Aug 1, 2026164 ms
Aug 8, 2026157 ms
Aug 15, 2026138 ms
Aug 22, 2026137 ms
Aug 29, 2026129 ms
Sep 5, 2026128 ms
Sep 12, 2026128 ms
Sep 19, 2026133 ms
Sep 26, 2026145 ms
Oct 3, 2026156 ms
Oct 10, 2026160 ms
Oct 17, 2026161 ms
Oct 24, 2026157 ms
Oct 31, 2026154 ms
Nov 7, 2026161 ms
Nov 14, 2026155 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

Full-page screenshot of adorracarpet.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adorracarpet.com at 1.8 s1.8 s
  2. adorracarpet.com at 3.7 s3.7 s
  3. adorracarpet.com at 5.5 s5.5 s
  4. adorracarpet.com at 7.3 s7.3 s
  5. adorracarpet.com at 9.2 s9.2 s
  6. adorracarpet.com at 11.0 s11.0 s
  7. adorracarpet.com at 12.8 s12.8 s
  8. adorracarpet.com at 14.7 s14.7 s

Speed

16 to fix35
  • Avoid multiple page redirects

    98.1 s

    The page goes through 1 redirect before it starts loading, costing about 98.1 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    7.8 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.8 s faster on a phone.

  • Main-thread work: 10.8 s

    A phone's processor spends 10.8 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 5,100 HTML elements

    The page has 5,100 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    700 ms · 2.1 MB

    14 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and zenythaudit.com and others), adding 3.8 MB and 2.3 s of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 580 KiB

    29 files are served with short cache lifetimes, so returning visitors download them again (580 KiB).

  • Render-blocking requests

    900 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Reduce unused CSS

    600 ms · 80 KiB

    About 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • alia-prod.com adds 515 ms

    515 ms

    alia-prod.com costs a phone 515 ms of main-thread work and 1.5 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 522 ms

    522 ms

    Google Tag Manager costs a phone 522 ms of main-thread work and 713 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.

  • zenythaudit.com adds 371 ms

    371 ms

    zenythaudit.com costs a phone 371 ms of main-thread work and 560 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.

  • Optanon adds 339 ms

    339 ms

    Optanon costs a phone 339 ms of main-thread work and 308 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.

  • Minify JavaScript

    300 ms · 48 KiB

    48 KiB could be saved by minifying JavaScript.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 322 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    58 KiB

    Polyfills for old browsers add 58 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: 24 ms

    24 ms

    Your server sent the HTML in 24 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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.

  • Real-user FCP: 3.2 s

    3.2 s

    Real visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 10.1 s

    10.1 s

    The first text or image appears after 10.1 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 105.2 s

    105.2 s

    Your largest element takes 105.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 36.0 s

    36.0 s

    Visually, the page fills in at 36.0 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 119.2 s

    119.2 s

    The page becomes fully interactive after 119.2 s. Good is under 3.8 s.

  • Total Blocking Time: 835 ms

    835 ms

    Scripts block taps and scrolling for 835 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.4 s

    3.4 s

    Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 154 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -5%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 180 ms

    180 ms

    Real visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 609 ms

    609 ms

    Real visitors wait 609 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.017

    0.017

    The layout barely moves while loading (CLS 0.017, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 40.1 MB in 1,075 requests

    40.1 MB

    Your homepage downloads 40.1 MB in 1,075 requests on a phone: images 33.4 MB (469), scripts 3.9 MB (186) and other files 1.7 MB (371). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (1.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.

  • About 11.4 g of CO₂ per visit

    11.38 g

    By the Sustainable Web Design model, a visit to your homepage emits about 11.38 g of CO₂e: 1365.1 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

3 to fixGoogle 9997
  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 347 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 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9283
  • Title is short (12 characters)

    Your title is only 12 characters: “STARK Carpet”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 9 H1 headlines

    There are 9 <h1> headlines (“Timeless in design, crafted to last generations.”, “Complimentary Samples” and “Trade Program”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 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.

  • 314 internal links, 5 external

    The homepage links to 314 pages on adorracarpet.com and 5 external pages.

5 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Visit STARK Carpet for the iconic patterns, designer collaborations and custom designs that will create unforgettable r…”.

  • Canonical URL set

    The canonical URL is https://starkcarpet.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://starkcarpet.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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,488 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://starkcarpet.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://starkcarpet.com/collections/stark-rugs has no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://starkcarpet.com/collections/bf-sale-all-rugs, https://starkcarpet.com/collections/custom-sized-rugs, https://starkcarpet.com/collections/rugs, https://starkcarpet.com/collections/stark-rugs, https://starkcarpet.com/collections/ashley-stark-home-rugs and https://starkcarpet.com/collections/stark-studio-rugs-collection and 4 others 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 117 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9279
  • 12 small tap targets

    12 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 766 words of copy

    The homepage carries about 766 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More” and “SHOP THE SALE”.

  • 27 calls to action

    The homepage has 27 calls to action, for example “Learn More”, “SHOP THE SALE” and “Start Shopping”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 21 testimonial or review blocks and 3 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Tag Manager, HubSpot, Klaviyo, Microsoft Clarity and Pinterest Tag (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 30 cookies set on arrival

    30

    Opening the homepage sets 30 cookies, 5 of them by other companies (measured from a US location before any click).

  • 51 other companies contacted

    Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 adorracarpet.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 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blockify Fraud Filter · Triplewhale · Analyzify Ga4 Ads Tracking · Attentive · Blockx Country Blocker · Checkmate · Klaviyo Email Marketing Sms · Region Restrictions · Restockrocket · attn.tv · cloudfront.net · octaneai.com · usemonocle.com · rebuyengine.com · hubapi.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
Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on adorracarpet.com, including 25 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25