runh.com website review

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

19 images could be 25.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

5 third-party services load with your homepage (Google Tag Manager, Baidu Analytics and Google Analytics and others), adding 569 KiB and 622 ms of main-thread time.

Google Tag Manager costs a phone 558 ms of main-thread work and 520 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 520 KiB of JavaScript is downloaded but never used on this page.

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

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

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

8 KiB could be saved by minifying CSS.

23 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

2 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 30.7 MB in 86 requests on a phone: images 28.8 MB (44), scripts 996 KiB (12) and media 795 KiB (1). Under 2 MB keeps phones on slow connections fast.

12 images weigh 26.5 MB together. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example a312c576bbcce46fdef339216e4aa161.png at 1,998 px wide, shown at 289 px. Resized copies would save about 7.0 MB.

24 images (28.5 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.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is 98 characters, so Google will cut it off around 60: “Coal-fired Power Plants Retrofit | Gas Turbine, Boiler | Power Station EPC Contractor - R…”.

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

Your meta description is 486 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

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

The homepage links to 74 pages on runh.com and 14 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.runh.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.

Your homepage links to https://www.runh.com/power-plant-series/small-sized-power-plant, https://www.runh.com/steam-turbine-island/steam-turbine-island, https://www.runh.com/steam-turbine-island/3, https://www.runh.com/boiler-island/8, https://www.runh.com/boiler-island/11 and https://www.runh.com/green-island/DeSOx and 4 others, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.runh.com/power-plant-series/6 and https://www.runh.com/power-plant-series/medium-sized-power-plant all use the title “EPC Power Plant Contractors | Design, Retrofitting & Relocation Exper…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.runh.com/power-plant-series/6 and https://www.runh.com/power-plant-series/medium-sized-power-plant use the same meta description. A description written for each page earns more clicks.

https://www.runh.com/power-plant-series/6, https://www.runh.com/power-plant-series/medium-sized-power-plant and https://www.runh.com/yuanhe have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.runh.com/power-plant-series/6 and https://www.runh.com/power-plant-series/medium-sized-power-plant took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

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