mycolorwheel.com website review

About 501 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Weebly, Google Tag Manager and Google CDN and others), adding 1.2 MB and 693 ms of main-thread time.

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

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

Google CDN costs a phone 122 ms of main-thread work and 348 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.

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

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

12 KiB could be saved by minifying JavaScript.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

Desktop scores 57 but mobile only 32. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Your largest element takes 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Beautiful Made Easy ​Since 1965 SHOP ONLINE FURNITURE SALE …”.

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

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

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

The layout shifts by 0.336 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.7 MB in 73 requests on a phone: images 4.4 MB (29), scripts 1.0 MB (16) and fonts 202 KiB (7). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

12 images (3.3 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.

10 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example wallpaper-brewster-0003-image-1_orig.jpg at 1,100 px wide, shown at 342 px. Resized copies would save about 102 KiB.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 18 characters: “Color Wheel - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

2 links have no real href, so search engines can't follow them.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 87 pages on mycolorwheel.com and 7 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.

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

/paint-supplies.html, /interior-paints.html, /paint-wallpaper-primer.html, /exterior-paints-fairfax-mclean-va.html, /clear-finishes--preservatives.html and /painting-supplies-fairfax-mclean-va.html and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/paint-supplies.html, /interior-paints.html, /paint-wallpaper-primer.html, /exterior-paints-fairfax-mclean-va.html, /clear-finishes--preservatives.html and /painting-supplies-fairfax-mclean-va.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

http://mycolorwheel.com does not redirect to https, so some visitors land on the insecure version.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

mycolorwheel.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

mycolorwheel.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

DMARC is set to p=none, so mail pretending to be mycolorwheel.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 8 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.