raregrp.com website review

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

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

About 627 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.7 s faster on a phone.

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

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

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

Reduce initial server response time. Google estimates savings of 1.0 s on a phone.

12 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 450 ms faster on a phone.

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

The page has 1,986 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

7 KiB could be saved by minifying CSS.

7 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (11.5 s).

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

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

Your homepage downloads 6.2 MB in 99 requests on a phone: images 3.9 MB (47), scripts 1.1 MB (22) and stylesheets 752 KiB (21). Under 2 MB keeps phones on slow connections fast.

11 images (1.8 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.

5 images further down the page (1.1 MB) 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 rare_logo-min.png at 2,560 px wide, shown at 26 px. Resized copies would save about 93 KiB.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

There are 2 <h1> headlines (“Premium IFM Solutions For Every Facility Needs” and “Proven Impact, Across Industries”). One clear main headline is easier for people and search engines.

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

The homepage links to 83 pages on raregrp.com and 8 external pages.

There is no https://raregrp.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.

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

The homepage carries about 522 words of visible text.

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