rsgx.com website review

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

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

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

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

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

287 KiB could be saved by minifying JavaScript.

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

Google Tag Manager costs a phone 449 ms of main-thread work and 863 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.

60 KiB could be saved by minifying CSS.

6 third-party services load with your homepage (Google Tag Manager, LinkedIn Ads and Cloudflare CDN and others), adding 947 KiB and 469 ms of main-thread time.

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

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 wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors wait 2.9 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

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

Your homepage downloads 17.4 MB in 100 requests on a phone: media 8.9 MB (1), images 5.0 MB (21) and scripts 1.8 MB (41). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example logo-rsgx-dark.png at 1,000 px wide, shown at 120 px. Resized copies would save about 252 KiB.

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

2 images further down the page (276 KiB) 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 4.94 g of CO₂e: 593.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

All page content should be contained by landmarks: 59 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.

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

Your title is only 26 characters: “Powering Energy Transition”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

5 links have no real href, so search engines can't follow them.

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

The homepage links to 51 pages on rsgx.com and 17 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://www.rsgx.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.rsgx.com/careers is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, https://www.rsgx.com/about-us, https://www.rsgx.com/what-we-do, https://www.rsgx.com/industries/infrastruture-rail, https://www.rsgx.com/industries/infrastructure-roads-and-tunnels and https://www.rsgx.com/industries/mining and 10 others all use the title “Powering Energy Transition”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rsgx.com/industries/mining, https://www.rsgx.com/industries/wastewater, https://www.rsgx.com/industries/data-centre and https://www.rsgx.com/industries/battery-energy-storage-system-bess have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.rsgx.com/about-us, https://www.rsgx.com/what-we-do, https://www.rsgx.com/industries/infrastruture-rail, https://www.rsgx.com/industries/infrastructure-roads-and-tunnels, https://www.rsgx.com/industries/renewables and https://www.rsgx.com/industries/transmission-distribution and 7 others took over 3 s to send their HTML from our server.

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

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 street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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.

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

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