roomstogokids.com website review

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

25 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (ContentSquare, Facebook and Amplitude Mobile Analytics and others), adding 1.5 MB and 932 ms of main-thread time.

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

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

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

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

37 KiB could be saved by minifying JavaScript.

11 KiB JavaScript is shipped twice across bundles.

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.

4 KiB could be saved by minifying CSS.

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 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “KIDS VETERANS DAY SALE & COUPONS. Red! White! Wow-worthy ki…”.

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

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

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

Real visitors wait 370 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-11-07, real Chrome visitors' tap response (inp) went from 276 ms to 367 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 8.1 MB in 253 requests on a phone: scripts 3.8 MB (79), images 3.4 MB (61) and other files 432 KiB (83). Under 2 MB keeps phones on slow connections fast.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (11 elements).

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

The homepage links to 236 pages on roomstogokids.com and 13 external pages.

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.

https://www.roomstogo.com/sales/coupons/veterans-day-kids/kd01, https://www.roomstogo.com/sales/coupons/veterans-day-kids/kd02 and https://www.roomstogo.com/sales/coupons/veterans-day-kids/kd03 have no <title>, so Google invents the link text in results.

https://www.roomstogo.com/sales/coupons/veterans-day-kids/kd01, https://www.roomstogo.com/sales/coupons/veterans-day-kids/kd02 and https://www.roomstogo.com/sales/coupons/veterans-day-kids/kd03 have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Error loading AWS RUM web client User is not trackable{"hasWebdriver":true,"isTrackable":false}”.

Large scripts ship without source maps.

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

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

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

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

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

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