sjggroup.com website review

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

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

About 3.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 18.2 s faster on a phone.

591 KiB could be saved by minifying CSS.

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

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

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

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

The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 566 ms on a phone.

Your server takes 666 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

25 KiB could be saved by minifying JavaScript.

2 long tasks block the main thread while loading, the longest for 111 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.

1 third-party service load with your homepage (Google Fonts), adding 37 KiB and 0 ms of main-thread time.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors see the first content after 6.2 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 41.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Discover the Heartbeat of SJG: Our Manufacturing Excellence”.

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

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

4 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-10, real Chrome visitors' tap response (inp) went from 117 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.9 MB in 91 requests on a phone: stylesheets 3.4 MB (31), images 2.8 MB (18) and scripts 1.0 MB (30). Under 2 MB keeps phones on slow connections fast.

3 images (917 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.

4 images further down the page (564 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example wall-design-e1697970419552.png at 1,200 px wide, shown at 340 px. Resized copies would save about 102 KiB.

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

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 10 pages on sjggroup.com and 2 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://sjggroup.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://sjggroup.com/about-us, https://sjggroup.com/company-history, https://sjggroup.com/careers, https://sjggroup.com/drug-safety and https://sjggroup.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

https://sjggroup.com/drug-safety took over 3 s to send its HTML from our server.

We fetched 5 pages linked from your homepage and read each the way a search engine does.

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

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.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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

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