moxionpower.com website review

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

2 images could be 516 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

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

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

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

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

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

5 third-party services load with your homepage (cdn-cookieyes.com, wpmucdn.com and Adobe TypeKit and others), adding 434 KiB and 60 ms of main-thread time.

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

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 45.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome You’ve been redirected to Viridi. If you were looki…”.

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

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

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

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

Your homepage downloads 10.6 MB in 111 requests on a phone: images 9.1 MB (13), fonts 822 KiB (10) and scripts 529 KiB (37). Under 2 MB keeps phones on slow connections fast.

2 images weigh 8.0 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example Flag-Logo-Horizontal.svg at 505 px wide, shown at 130 px. Resized copies would save about 2.1 MB.

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

2 images (720 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.

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

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

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h4 and h3 → h6), 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.

Your title is only 23 characters: “Moxion-Inquire – Viridi”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 103 pages on moxionpower.com and 14 external pages.

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

https://viridiparente.com/products and https://viridiparente.com/faq have no meta description, so Google writes the search snippet from whatever text it finds.

https://viridiparente.com/viridi-takes-over-moxion-hq-secures-9-3m-cec-grant and https://viridiparente.com/power-that-pays-for-itself use the same meta description. A description written for each page earns more clicks.

https://viridiparente.com/faq has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

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.

The homepage shows no opening hours. If customers visit or call, show when.

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 3 cookies (measured from a US location before any click).

Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.