ssr-inc.com website review

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

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

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

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

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

64 KiB could be saved by minifying JavaScript.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 266 KiB and 113 ms of main-thread time.

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

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 33.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Innovative and sustainable solutions delivered by a passion…”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 images weigh 28.3 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example 16640860_N57.jpg at 10,756 px wide, shown at 350 px. Resized copies would save about 20.5 MB.

Your homepage downloads 10.9 MB in 68 requests on a phone: images 10.1 MB (32), scripts 449 KiB (17) and fonts 193 KiB (6). Under 2 MB keeps phones on slow connections fast.

20 images (30.4 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.

7 images further down the page (22.4 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 3.09 g of CO₂e: 371.1 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.

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

Some list items are not inside a list.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

Your title is only 15 characters: “SSR - We Own It”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 87 pages on ssr-inc.com and 7 external pages.

There is no https://www.ssr-inc.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.ssr-inc.com/what-we-do, https://www.ssr-inc.com/what-we-do/design, https://www.ssr-inc.com/what-we-do/consulting, https://www.ssr-inc.com/what-we-do/planning, https://www.ssr-inc.com/who-we-serve and https://www.ssr-inc.com/who-we-serve/civic-community and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ssr-inc.com/who-we-serve has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 37 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”.

Large scripts ship without source maps.

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

Social proof on the homepage: 14 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads 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 3 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.