goldplusgroup.com website review

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

21 images could be 3.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.8 s faster on a phone.

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

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

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

29 KiB could be saved by minifying JavaScript.

1 long task block the main thread while loading, the longest for 157 ms. During a long task the page ignores taps.

5 third-party services load with your homepage (GoDaddy, JSDelivr CDN and Cloudflare CDN and others), adding 210 KiB and 75 ms of main-thread time.

About 18 KiB of CSS is downloaded but never applied on this page.

Desktop scores 67 but mobile only 39. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying CSS.

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

For real visitors the layout shifts by 0.87 (75th percentile). Good is under 0.1.

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

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

The layout shifts by 0.883 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Logo”. Most of its time is resource load delay (8.8 s).

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

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

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

13 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 86 ms to 87 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.7 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 22.2 MB in 58 requests on a phone: media 17.6 MB (2), images 4.2 MB (30) and scripts 210 KiB (13). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

12 images (4.0 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.

12 images further down the page (3.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

7 images are downloaded at several times the size a phone draws them, for example chairman.png at 894 px wide, shown at 296 px. Resized copies would save about 328 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

4 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.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 15 characters: “Gold Plus 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.

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

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

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

The homepage links to 73 pages on goldplusgroup.com and 6 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 /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.

/, /plants, /careers and /csr all use the title “Gold Plus Group”. Search engines can't tell which page to show for a search, so each competes with the others.

/plants, /careers and /csr have no meta description, so Google writes the search snippet from whatever text it finds.

/plants, /careers and /csr took over 3 s to send their HTML from our server.

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

2 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

goldplusgroup.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

goldplusgroup.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 3 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.