sarasells.com website review

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

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

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

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

Google Fonts costs a phone 2 ms of main-thread work and 298 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 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

8 third-party services load with your homepage (Amazon Web Services, JSDelivr CDN and Shopify and others), adding 676 KiB and 211 ms of main-thread time.

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

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

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

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

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

6 images are downloaded at several times the size a phone draws them, for example banner-img.jpg at 4,096 px wide, shown at 390 px. Resized copies would save about 1.3 MB.

banner-img.jpg weighs 693 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.4 MB in 181 requests on a phone: images 1.7 MB (8), other files 743 KiB (84) and scripts 408 KiB (43). Under 2 MB keeps phones on slow connections fast.

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Your title is only 10 characters: “Sara Sells”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “Birmingham Sale”). One clear main headline is easier for people and search engines.

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

The homepage links to 36 pages on sarasells.com and 16 external pages.

https://sarasells.com/pages/about-us, https://sarasells.com/pages/nashville, https://sarasells.com/pages/birmingham, https://sarasells.com/pages/memphis, https://sarasells.com/pages/trade and https://sarasells.com/collections/living and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://sarasells.com/pages/about-us, https://sarasells.com/pages/nashville, https://sarasells.com/pages/birmingham, https://sarasells.com/pages/memphis, https://sarasells.com/pages/trade and https://sarasells.com/collections/living and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sarasells.com/collections/living, https://sarasells.com/collections/dining, https://sarasells.com/collections/lighting, https://sarasells.com/collections/kitchen, https://sarasells.com/collections/bed and https://sarasells.com/collections/decor and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

3 errors were logged to the browser console while the page loaded, for example “Identifier 'getBrowserLanguage' has already been declared”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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 9 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.