castlef.com website review

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

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

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

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

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

8 third-party services load with your homepage (Clarity, Google Tag Manager and sovrn and others), adding 472 KiB and 397 ms of main-thread time.

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

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

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

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

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

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 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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 2.3 MB in 175 requests on a phone: other files 754 KiB (98), images 735 KiB (22) and scripts 429 KiB (29). Under 2 MB keeps phones on slow connections fast.

1 image (81 KiB) is 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.66 g of CO₂e: 79.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

11 visible links have no text or label, so screen readers cannot say where they go.

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

Your canonical URL points to castlefurniture.com, not castlef.com, so Google may credit that host instead.

Structured data found (FurnitureStore, LocalBusiness, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://castlefurniture.com/)”.

The homepage links to 189 pages on castlef.com and 22 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

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

4 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 “Access to XMLHttpRequest at 'https://cdn.endorsal.io/widgets/endorsal-testimonials.min.css' from origin 'https://castle…”.

1 image is served at too low a resolution for sharp phone screens.

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

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