3phasesrenewables.com website review

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, ShareThis and LinkedIn Ads and others), adding 583 KiB and 540 ms of main-thread time.

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

143 KiB could be saved by minifying JavaScript.

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

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

1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

16 KiB could be saved by minifying CSS.

Polyfills for old browsers add 22 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.

Your largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “3 Phases Renewables is a leading supplier of comprehensive …”. Most of its time is element render delay (6.5 s).

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

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

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

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

4 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 7.5 MB in 73 requests on a phone: media 5.4 MB (2), scripts 1.2 MB (33) and images 406 KiB (9). Under 2 MB keeps phones on slow connections fast.

2 images (65 KiB) 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.

2 images further down the page (52 KiB) 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 2.12 g of CO₂e: 254.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.

1 image has 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.

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.

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.

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

The homepage links to 23 pages on 3phasesrenewables.com and 0 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/direct-access, /distributed-generation, /clean-transportation, /wholesale-market-services, /environmental-commodity-products and /about-us and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/direct-access, /distributed-generation, /clean-transportation, /wholesale-market-services, /environmental-commodity-products and /about-us and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

/contact-us, /careers and /faq have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://3phasesrenewables.com' has been bl…”.

Large scripts ship without source maps.

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.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

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.

3phasesrenewables.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.

3phasesrenewables.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.

Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

DMARC is set to p=none, so mail pretending to be 3phasesrenewables.com is still delivered. Add a report address, check the reports, then move to quarantine.

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.

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