riverstreetsweets.com website review

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

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

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

8 third-party services load with your homepage (minmaxify.com, alia-prod.com and Shopify and others), adding 2.0 MB and 3.0 s of main-thread time.

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

minmaxify.com costs a phone 789 ms of main-thread work and 9 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.

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

alia-prod.com costs a phone 637 ms of main-thread work and 844 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.

Shopify costs a phone 543 ms of main-thread work and 394 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 343 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Klaviyo costs a phone 278 ms of main-thread work and 297 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.

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

Facebook costs a phone 277 ms of main-thread work and 201 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 36 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.

Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need.

24 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.

5 KiB could be saved by minifying JavaScript.

3 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Your homepage downloads 6.3 MB in 402 requests on a phone: images 3.3 MB (38), scripts 1.6 MB (162) and other files 877 KiB (167). Under 2 MB keeps phones on slow connections fast.

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

ARIA commands must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

Your title is 70 characters, so Google will cut it off around 60: “River Street Sweets® | Savannah's World Famous Pralines & Southern Can”.

Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.riverstreetsweets.com")”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 169 pages on riverstreetsweets.com and 10 external pages.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

The homepage has only about 18 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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