Website review, no card needed

greenice.com logo

greenice.com website review

Visit site (opens in a new tab)Reviewed 5 November 202640 issues · 89 checks

This review found 40 issues worth fixing on greenice.com, 16 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
2.9 s2.4 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
299 ms228 msMay 16Oct 31284 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026244 ms
May 23, 2026236 ms
May 30, 2026239 ms
Jun 6, 2026242 ms
Jun 13, 2026248 ms
Jun 20, 2026252 ms
Jun 27, 2026255 ms
Jul 4, 2026257 ms
Jul 11, 2026257 ms
Jul 18, 2026260 ms
Jul 25, 2026259 ms
Aug 1, 2026259 ms
Aug 8, 2026266 ms
Aug 15, 2026273 ms
Aug 22, 2026278 ms
Aug 29, 2026288 ms
Sep 5, 2026287 ms
Sep 12, 2026283 ms
Sep 19, 2026283 ms
Sep 26, 2026282 ms
Oct 3, 2026287 ms
Oct 10, 2026288 ms
Oct 17, 2026291 ms
Oct 24, 2026290 ms
Oct 31, 2026284 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 greenice.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. greenice.com at 1.0 s1.0 s
  2. greenice.com at 2.1 s2.1 s
  3. greenice.com at 3.1 s3.1 s
  4. greenice.com at 4.2 s4.2 s
  5. greenice.com at 5.2 s5.2 s
  6. greenice.com at 6.3 s6.3 s
  7. greenice.com at 7.3 s7.3 s
  8. greenice.com at 8.3 s8.3 s

Speed

12 to fix30
  • Use efficient cache lifetimes

    1.4 s · 560 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 8.6 s

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

  • 8,058 HTML elements

    The page has 8,058 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 (Convert Insights, Google Tag Manager and kimeratechnologies.com and others), adding 1.6 MB and 2.2 s of main-thread time.

  • Convert Insights adds 946 ms

    946 ms

    Convert Insights costs a phone 946 ms of main-thread work and 63 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.

  • Reduce unused JavaScript

    150 ms · 737 KiB

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

  • Google Tag Manager adds 350 ms

    350 ms

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

  • kimeratechnologies.com adds 243 ms

    243 ms

    kimeratechnologies.com costs a phone 243 ms of main-thread work and 431 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.

  • Google CDN adds 205 ms

    205 ms

    Google CDN costs a phone 205 ms of main-thread work and 298 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.

  • Shopify adds 172 ms

    172 ms

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

  • 20 long tasks on the main thread

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

  • Improve image delivery

    229 KiB

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

  • Legacy JavaScript

    150 ms · 9 KiB

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

  • Reduce unused CSS

    40 KiB

    About 40 KiB of CSS is downloaded but never applied on this page.

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

  • 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 65 ms

    65 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Time to Interactive: 23.4 s

    23.4 s

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

  • Largest Contentful Paint: 7.1 s

    7.1 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user INP: 327 ms

    327 ms

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

  • Tap response (INP) got 20% slower for real visitors

    +20%

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

  • Cumulative Layout Shift: 0.222

    0.222

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 1 image without width and height

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 581 ms

    581 ms

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

Images and page weight

2 to fix64
  • Page weight: 4.7 MB in 522 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 522 requests on a phone: images 1.7 MB (272), scripts 1.7 MB (91) and other files 946 KiB (97). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    proyectoressolares-202507Jul_HOMEMOBILE.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.3 g of CO₂ per visit

    1.34 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 8191
  • 138 text elements with low contrast

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

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

  • 11 links without text

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

  • 8 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 364 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 711 internal links, 5 external

    The homepage links to 711 pages on greenice.com and 5 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “En GreenIce somos especialistas en Iluminación LED. Gran catálogo en Bombillas Led, Lámparas Led, Focos Led, Downlights…”.

  • One H1 headline

    Your main headline reads: “ILUMINACIÓN LED”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “GreenIce: Tienda Online de Luces LED | Iluminación LED”.

  • Canonical URL set

    The canonical URL is https://greenice.com/.

  • 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://greenice.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    /collections/all and /policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    /collections/all, /policies/shipping-policy, /collections/bombillas-led-702, /collections/bombillas-led-e27-761, /collections/bombillas-led-e14-760 and /collections/bombillas-led-gu10-764 and 8 others 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 199 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 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 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://greenice.com/cdn/shop/t/110/assets/ma.svg?v=730559.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    51 of 55 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,909 words of copy

    The homepage carries about 1,909 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now”.

  • 1 call to action

    The homepage has 1 call to action, for example “Shop now”.

  • 6 short forms

    6 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 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.

  • 39 other companies contacted

    Loading the homepage contacts 39 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 greenice.com, 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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Planet Discounts Upsells · Upango Cestas Greenice · Planetdataset App · Orbe Geolocation · Revi Store Product Reviews For Ecommerce · azurewebsites.net · trustpilot.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
Bootstrap
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on greenice.com, including 22 speed issues and 2 SEO issues. 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