Website review, no card needed

iallpowers.eu logo

iallpowers.eu website review

Visit site (opens in a new tab)Reviewed 5 November 202643 issues · 85 checks

This review found 43 issues worth fixing on iallpowers.eu, 18 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.8 s5.7 sMay 16Oct 316.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20266.3 s
May 23, 20266.3 s
May 30, 20266.3 s
Jun 6, 20266.4 s
Jun 13, 20266.4 s
Jun 20, 20266.4 s
Jun 27, 20266.4 s
Jul 4, 20266.2 s
Jul 11, 20266.1 s
Jul 18, 20266.1 s
Jul 25, 20266.2 s
Aug 1, 20266.2 s
Aug 8, 20266.4 s
Aug 15, 20266.2 s
Aug 22, 20266.0 s
Aug 29, 20266.0 s
Sep 5, 20265.9 s
Sep 12, 20266.0 s
Sep 19, 20266.2 s
Sep 26, 20266.2 s
Oct 3, 20266.3 s
Oct 10, 20266.3 s
Oct 17, 20266.4 s
Oct 24, 20266.7 s
Oct 31, 20266.7 s
Real-visitor tap response (INP)75th percentile, phones
567 ms242 msMay 16Oct 31302 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026529 ms
May 23, 2026525 ms
May 30, 2026511 ms
Jun 6, 2026515 ms
Jun 13, 2026505 ms
Jun 20, 2026499 ms
Jun 27, 2026502 ms
Jul 4, 2026443 ms
Jul 11, 2026371 ms
Jul 18, 2026327 ms
Jul 25, 2026296 ms
Aug 1, 2026287 ms
Aug 8, 2026293 ms
Aug 15, 2026292 ms
Aug 22, 2026287 ms
Aug 29, 2026286 ms
Sep 5, 2026279 ms
Sep 12, 2026281 ms
Sep 19, 2026291 ms
Sep 26, 2026296 ms
Oct 3, 2026300 ms
Oct 10, 2026301 ms
Oct 17, 2026300 ms
Oct 24, 2026303 ms
Oct 31, 2026302 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of iallpowers.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. iallpowers.eu at 0.9 s0.9 s
  2. iallpowers.eu at 1.8 s1.8 s
  3. iallpowers.eu at 2.7 s2.7 s
  4. iallpowers.eu at 3.5 s3.5 s
  5. iallpowers.eu at 4.4 s4.4 s
  6. iallpowers.eu at 5.3 s5.3 s
  7. iallpowers.eu at 6.2 s6.2 s
  8. iallpowers.eu at 7.1 s7.1 s

Speed

12 to fix38
  • Reduce unused JavaScript

    5.7 s · 1.2 MB

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

  • Use efficient cache lifetimes

    2.6 s · 434 KiB

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

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 9.7 s

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

  • 5,549 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 3.0 MB and 2.2 s of main-thread time.

  • Shopify adds 881 ms

    881 ms

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

  • Google Tag Manager adds 588 ms

    588 ms

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

  • Minify JavaScript

    310 ms · 60 KiB

    60 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    350 ms

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

  • 20 long tasks on the main thread

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

  • Klaviyo adds 247 ms

    247 ms

    Klaviyo costs a phone 247 ms of main-thread work and 312 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.

  • Improve image delivery

    212 KiB

    5 images could be 212 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    150 ms · 45 KiB

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

  • Legacy JavaScript

    150 ms · 31 KiB

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

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 14 ms

    14 ms

    Your server sent the HTML in 14 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix0
  • Fails Core Web Vitals for real visitors

    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-user LCP: 5.8 s

    5.8 s

    Real visitors wait 5.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 6.0 s

    6.0 s

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

  • Largest Contentful Paint: 27.6 s

    27.6 s

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

  • Time to Interactive: 29.1 s

    29.1 s

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

  • Speed Index: 13.4 s

    13.4 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Real-user INP: 257 ms

    257 ms

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

  • Real-user CLS: 0.21

    0.21

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

  • Real-user TTFB: 844 ms

    844 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

2 checks passed
  • Tap response (INP) got 43% faster for real visitors

    -43%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 529 ms to 302 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 10.6 MB in 266 requests

    10.6 MB

    Your homepage downloads 10.6 MB in 266 requests on a phone: media 5.2 MB (1), scripts 3.2 MB (120) and images 1.0 MB (26). Under 2 MB keeps phones on slow connections fast.

  • About 3.0 g of CO₂ per visit

    3.00 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 7991
  • 1 button without a name

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8586
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Buy ALLPOWERS® Solar Generator Portable Power Station & Solar Panels”.

  • 25 links with vague text

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

  • Meta description is long (278 characters)

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

  • 622 internal links, 26 external

    The homepage links to 622 pages on iallpowers.eu and 26 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “ALLPOWERS EU”.

  • Canonical URL set

    The canonical URL is https://iallpowers.eu/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://iallpowers.eu/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,194 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://iallpowers.eu/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 1 page without a meta description

    https://iallpowers.eu/collections/balcony-solar-system has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://iallpowers.eu/collections/camping-outdoor and https://iallpowers.eu/collections/home-backup use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://iallpowers.eu/pages/black-friday, https://iallpowers.eu/collections/camping-outdoor, https://iallpowers.eu/collections/home-backup, https://iallpowers.eu/collections/balcony-solar-system and https://iallpowers.eu/collections/solar-generator have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=&referrer=&landingpage=https%3A%2F%2Fiallpowers.eu%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017_5%20like%20Mac%20OS%20X)%20AppleWebK.

  • 12 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Unexpected number”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

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

  • No direct contact details

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

  • About 405 words of copy

    The homepage carries about 405 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get My Discount”.

  • 70 calls to action

    The homepage has 70 calls to action, for example “Learn More”, “Contact Us” and “Warranty Register”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel and Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    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.

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    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.

  • 38 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at iallpowers.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 28 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Klaviyo Email Marketing Sms · Ta Labels Badges · Bundler Bundles App · Seowill Ai Seo · Pagefly Ai Page Builder · Ta Banner Pop Up · Bss B2b Quotes · Gsc Countdown Timer · Pixee Facebook Pixel · Awin Affiliate Marketing · Gdpr Cookie Consent · Pdf Invoice Customizer · Tms Prod V 3c482b6 · Event Promotion Bar · Avada Faqs · Freegifts · Restockrocket · Ecomsend · goaffpro.com · nice-team.net · cloudfront.net · bogos.io · hextom.com · loox.io · conversionbear.com · attribuly.com · webgains.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on iallpowers.eu, including 23 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25