rahee.com website review

About 148 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.

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

About 58 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.

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

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 179 KiB and 129 ms of main-thread time.

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Track by top railroad company Rahee”.

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

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

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

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.

ng1.7fbdf3ee.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example banner.53caaa19.webp at 1,920 px wide, shown at 390 px. Resized copies would save about 45 KiB.

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

4 images have no alt text, which hurts accessibility and image search.

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

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

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

Structured data found (FAQPage, LocalBusiness, Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("{search_term_string}")”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 120 pages on rahee.com and 9 external pages.

https://rahee.com/blog/blog1 and https://rahee.com/blog/blog2 have no <title>, so Google invents the link text in results.

https://rahee.com/blog/blog1 and https://rahee.com/blog/blog2 have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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