riterug.com website review

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

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

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

Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

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

134 KiB could be saved by minifying JavaScript.

About 295 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

6 third-party services load with your homepage (Google Tag Manager, Google Fonts and Shopify and others), adding 1.3 MB and 356 ms of main-thread time.

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

58 KiB could be saved by minifying CSS.

Shopify costs a phone 0 ms of main-thread work and 717 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.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A study with a herringbone hardwood floor and a RiteRug are…”.

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

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

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

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

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

Your homepage downloads 2.8 MB in 62 requests on a phone: images 1.6 MB (21), scripts 857 KiB (13) and stylesheets 206 KiB (4). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example 5153d8e7b0947ae73688d94e956849a72dd59656.jpg at 1,100 px wide, shown at 362 px. Resized copies would save about 51 KiB.

2 images (191 KiB) 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.

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

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

Your title is 67 characters, so Google will cut it off around 60: “RiteRug Flooring | Carpet, Tile, Hardwood, Vinyl, Laminate Flooring”.

Your meta description is 288 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 151 pages on riterug.com and 0 external pages.

/pages/appointments and /visualizer all use the title “Appointments | RiteRug Flooring”. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/appointments and /visualizer use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /visualizer, whose canonical is /pages/appointments. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/appointments, /pages/locations, /pages/customer-care, /visualizer, /collections/5-x-7-rugs and /collections/7-x-10-rugs and 1 other took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187018247&tm=gtm002&Ver=2&mid=6397b041-d77b-40c4-a817-2bb2500d0209&bo=1&sid=1cc1fab0d97711f18ebc47e948572fee&vid=1cc21920d97711f1918f179f4a61f246&vids=1&msclkid=N&pi=9.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 874 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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