ruggable.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Klaviyo and others), adding 1.3 MB and 1.3 s of main-thread time.

12 images could be 550 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

Polyfills for old browsers add 101 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

cloudfront.net costs a phone 257 ms of main-thread work and 43 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.

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

Constructor.io costs a phone 60 ms of main-thread work and 301 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.

12 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

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

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

Your homepage downloads 24.4 MB in 241 requests on a phone: media 17.9 MB (2), scripts 3.0 MB (118) and other files 1.7 MB (76). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 6.92 g of CO₂e: 830.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

7 tap targets are too small or too close together to hit reliably with a finger.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with visible text labels do not have matching accessible names. (1 element).

There are 3 <h1> headlines (“Washable Rugs”, “Up to 40% Off” and “Up to 40% Off”). One clear main headline is easier for people and search engines.

The homepage links to 289 pages on ruggable.com and 8 external pages.

There is no https://ruggable.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.

We fetched 15 pages linked from your homepage (of 95 found) and read each the way a search engine does.

3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=6025564&tm=gtm002&Ver=2&mid=b86ec48a-2f7c-4bb6-8f36-8e640a8f9665&bo=1&sid=0ac9dda0d80a11f19d12658545325d1c&vid=0aca13b0d80a11f1be72abd3939751cc&vids=1&msclkid=N&page_p.

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

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

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 425 words of visible text.

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

Before a visitor clicks anything, the page loads Amazon Ads, Amplitude, Google Ads, Google Analytics and Google Tag Manager and 2 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.

Opening the homepage sets 43 cookies (measured from a US location before any click).

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.

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