powur.com website review

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

About 1.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.3 s faster on a phone.

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

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

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

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

5 third-party services load with your homepage (Stripe, Vimeo and Google Tag Manager and others), adding 12.6 MB and 760 ms of main-thread time.

4 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Vimeo costs a phone 198 ms of main-thread work and 12.1 MB 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.

180 KiB could be saved by minifying CSS.

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

Stripe costs a phone 406 ms of main-thread work and 290 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.

Polyfills for old browsers add 53 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Your largest element takes 42.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Powur”.

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

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

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

Real visitors wait 304 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

7 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' largest content (lcp) went from 4.1 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 26.8 MB in 81 requests on a phone: other files 11.0 MB (32), images 7.4 MB (16) and scripts 7.3 MB (14). Under 2 MB keeps phones on slow connections fast.

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

7 buttons have no accessible name, so screen readers announce just “button”.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 12 characters: “powur energy”. 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 65 characters: “Powur: Accelerating the adoption of sustainable energy worldwide.”. 70 to 160 characters is enough to sell the click.

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

A phone browser shows 735 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://powur.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.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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