Website review, no card needed

earthlets.dk logo

earthlets.dk website review

Visit site (opens in a new tab)Reviewed 20 November 202640 issues · 88 checks

This review found 40 issues worth fixing on earthlets.dk, 15 of them high impact, across 88 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
1.9 s1.6 sMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Nov 7, 20261.8 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
238 ms188 msMay 30Nov 14232 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026194 ms
Jun 6, 2026198 ms
Jun 13, 2026212 ms
Jun 20, 2026207 ms
Jun 27, 2026204 ms
Jul 4, 2026203 ms
Jul 11, 2026199 ms
Jul 18, 2026198 ms
Jul 25, 2026207 ms
Aug 1, 2026206 ms
Aug 8, 2026218 ms
Aug 15, 2026223 ms
Aug 22, 2026220 ms
Aug 29, 2026227 ms
Sep 5, 2026208 ms
Sep 12, 2026199 ms
Sep 19, 2026196 ms
Sep 26, 2026196 ms
Oct 3, 2026210 ms
Oct 10, 2026218 ms
Oct 17, 2026215 ms
Oct 24, 2026215 ms
Oct 31, 2026205 ms
Nov 7, 2026205 ms
Nov 14, 2026232 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 earthlets.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. earthlets.dk at 4.2 s4.2 s
  2. earthlets.dk at 8.4 s8.4 s
  3. earthlets.dk at 12.7 s12.7 s
  4. earthlets.dk at 16.9 s16.9 s
  5. earthlets.dk at 21.1 s21.1 s
  6. earthlets.dk at 25.3 s25.3 s
  7. earthlets.dk at 29.6 s29.6 s
  8. earthlets.dk at 33.8 s33.8 s

Speed

16 to fix40
  • Reduce unused JavaScript

    6.2 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 6.2 s faster on a phone.

  • Use efficient cache lifetimes

    2.1 s · 641 KiB

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

  • Main-thread work: 24.0 s

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

  • POWr adds 1.7 s

    1.7 s

    POWr costs a phone 1.7 s of main-thread work and 13 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 40

    40/100

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

  • 7,237 HTML elements

    The page has 7,237 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 (POWr, Shopify and Clarity and others), adding 3.5 MB and 3.3 s of main-thread time.

  • Reduce unused CSS

    900 ms · 217 KiB

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

  • Improve image delivery

    400 ms · 590 KiB

    28 images could be 590 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Shopify adds 597 ms

    597 ms

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

  • Minify CSS

    440 ms · 114 KiB

    114 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    300 ms · 81 KiB

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

  • Clarity adds 348 ms

    348 ms

    Clarity costs a phone 348 ms of main-thread work and 30 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 Tag Manager adds 295 ms

    295 ms

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

  • amaicdn.com adds 267 ms

    267 ms

    amaicdn.com costs a phone 267 ms of main-thread work and 399 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

    150 ms · 54 KiB

    54 KiB could be saved by minifying JavaScript.

  • 20 long tasks on the main thread

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

  • Duplicated JavaScript

    43 KiB

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

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 25.2 s

    25.2 s

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

  • Time to Interactive: 37.9 s

    37.9 s

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

  • Speed Index: 10.7 s

    10.7 s

    Visually, the page fills in at 10.7 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: 264 ms

    264 ms

    Real visitors wait 264 ms for the page to respond to a tap (75th percentile). Good is under 200 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.

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

    +11%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (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: 600 ms

    600 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

1 to fix70
  • Page weight: 8.1 MB in 667 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 667 requests on a phone: scripts 3.0 MB (225), other files 2.4 MB (328) and images 2.1 MB (79). Under 2 MB keeps phones on slow connections fast.

  • About 2.3 g of CO₂ per visit

    2.30 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.30 g of CO₂e: 276.2 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

3 to fixGoogle 8996
  • 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.

  • 3 text elements with low contrast

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

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 115 images in the HTML carry an alt attribute.

  • 30 automated accessibility rules passed

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

SEO

4 to fixGoogle 9284
  • 2 H1 headlines

    There are 2 <h1> headlines (“Earthlets” and “What our customers say”). One clear main headline is easier for people and search engines.

  • Meta description is long (228 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 510 internal links, 14 external

    The homepage links to 510 pages on earthlets.dk and 14 external pages.

5 checks passed
  • Title: 53 characters

    Your title is a healthy 53 characters: “Trading Cards, Roblox Toys & Collectibles | Earthlets”.

  • Canonical URL set

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

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

AI search readiness

1 to fix83
  • Organization data is thin (0 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, 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.

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

  • llms.txt published

    The site publishes https://earthlets.com/llms.txt (19 KiB, 59 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9674
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97154892&Ver=2&mid=e7fb87dd-1a66-4557-8c42-763c30e519b8&bo=1&sid=67b016a0e4d911f1bd99d308558a2701&vid=67b034a0e4d911f1ad6695bb7a59eb22&vids=1&msclkid=N&pi=918639831&lg.

  • 5 JavaScript errors while loading

    5 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 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • Only about 23 words

    The homepage has only about 23 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

4 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop by Type”, “Shop by Brand” and “Shop by Scale”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 1 of them by other companies (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.

  • 44 other companies contacted

    Loading the homepage contacts 44 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 earthlets.dk, 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 27 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Blockify Fraud Filter · Lucky Orange · Bundler Bundles App · Multifeeds · Frequently Bought · Transcy · Also Bought · The Amp App · Analyzify Ga4 Ads Tracking · Smart Seo · Gdpr Cookie Consent · Region Restrictions · Frontend · Forms · Swym Wishlist Plus · Page Speed Optimizer · Freegifts · Reviews Co Uk Product And Merchant Review Collection · Jobly Career Page Builder · paypal.com · powr.io · trustpilot.com · negate.io · amazonaws.com · bogos.io · nice-team.net

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 Analytics
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 earthlets.dk, including 23 speed issues, 4 SEO issues and 5 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