theregencygroup.net website review

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

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

164 KiB could be saved by minifying JavaScript.

Google CDN costs a phone 1.1 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 29 (desktop: 32). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

7 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

20 long tasks block the main thread while loading, the longest for 2.1 s. During a long task the page ignores taps.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Maps and others), adding 1.9 MB and 1.8 s of main-thread time.

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

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

8 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

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

9 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 5.7 MB in 94 requests on a phone: images 2.4 MB (33), scripts 2.2 MB (25) and other files 449 KiB (13). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example 35d9b8971e91c1c3e3b942c7ea2c00e8.jpg at 925 px wide, shown at 126 px. Resized copies would save about 1.5 MB.

35d9b8971e91c1c3e3b942c7ea2c00e8.jpg weighs 992 KiB. On a phone connection a single image that size takes seconds.

6 images (1.9 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.

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

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

25 images have 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.

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

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

Your title is only 24 characters: “Home - The Regency Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 33 characters: “Regency group hotels landing page”. 70 to 160 characters is enough to sell the click.

There are 5 <h1> headlines (“Bringing your Brand to Life”, “WHAT WE DO” and “Featured Projects”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No XML sitemap at https://theregencygroup.net/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at theregencygroup.net/robots.txt, the first file search crawlers ask for.

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

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

The homepage links to 12 pages on theregencygroup.net and 5 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://theregencygroup.net/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://theregencygroup.net/gallery.php has no <title>, so Google invents the link text in results.

https://theregencygroup.net/gallery.php has no meta description, so Google writes the search snippet from whatever text it finds.

https://theregencygroup.net/gallery.php has no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

8 images are 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 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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 174 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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