the5thstreetgroup.com website review

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

6 third-party services load with your homepage (getbento.com, Google CDN and Other Google APIs/SDKs and others), adding 4.9 MB and 877 ms of main-thread time.

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

Your mobile performance score is 61 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

getbento.com costs a phone 559 ms of main-thread work and 3.8 MB 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 800 KiB of JavaScript is downloaded but never used on this page.

11 images could be 531 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google CDN costs a phone 282 ms of main-thread work and 734 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 81 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 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Desktop scores 90 but mobile only 61. 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.

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

Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “5th Street Group Home”.

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

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

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

11 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.2 MB in 57 requests on a phone: scripts 2.5 MB (12), images 1.8 MB (24) and fonts 545 KiB (9). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 42306image_1.png at 1,743 px wide, shown at 317 px. Resized copies would save about 237 KiB.

3 images (422 KiB) 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.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 16 characters: “5th Street Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Home” and “5th Street Group”). One clear main headline is easier for people and search engines.

The homepage links to 25 pages on the5thstreetgroup.com and 6 external pages.

There is no https://www.the5thstreetgroup.com/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.

https://www.the5thstreetgroup.com/restaurants, https://www.the5thstreetgroup.com/about, https://www.the5thstreetgroup.com/press, https://www.the5thstreetgroup.com/charleston-sc, https://www.the5thstreetgroup.com/nashville-tn and https://www.the5thstreetgroup.com/charlotte-nc and 3 others use the same meta description. A description written for each page earns more clicks.

https://www.the5thstreetgroup.com/press and https://www.the5thstreetgroup.com/reservations have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.the5thstreetgroup.com/press and https://www.the5thstreetgroup.com/reservations 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 9 pages linked from your homepage and read each the way a search engine does.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 has only about 124 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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