shopprojectsolar.com website review

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

8 third-party services load with your homepage (Shopify, Klaviyo and gemcommerce.com and others), adding 21.3 MB and 311 ms of main-thread time.

Shopify costs a phone 104 ms of main-thread work and 20.8 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.

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

13 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

12 images could be 507 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.

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

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

The page has 2,235 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Power Bank 2000”.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 25.5 MB in 424 requests on a phone: media 21.7 MB (4), images 1.6 MB (70) and other files 1.1 MB (200). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example EZCART_1024x1024.png at 1,013 px wide, shown at 67 px. Resized copies would save about 366 KiB.

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

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

2 dropdowns have no label.

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

2 images have no alt text, which hurts accessibility and image search.

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

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

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

54 links have no real href, so search engines can't follow them.

There are 7 <h1> headlines (“”, “Power Bank600” and “Power Bank 2000”). One clear main headline is easier for people and search engines.

Your meta description is 272 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 64 pages on shopprojectsolar.com and 8 external pages.

https://shopprojectsolar.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://shopprojectsolar.com/products/q-cell-monocrystalline-panel declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://shopprojectsolar.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://shopprojectsolar.com/products/q-cell-monocrystalline-panel all use the title “Project Solar – Shop Project Solar”. Search engines can't tell which page to show for a search, so each competes with the others.

https://shopprojectsolar.com/collections/all and https://shopprojectsolar.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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 15 cookies, 1 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.