Website review, no card needed

beachsim.de logo

beachsim.de website review

Visit site (opens in a new tab)Reviewed 9 November 202619 issues · 92 checks

This review found 19 issues worth fixing on beachsim.de, 4 of them high impact, across 92 checks. The most urgent: 1 text element with low contrast. 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.0 s1.5 sMay 23Nov 71.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.7 s
Nov 7, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
197 ms138 msMay 23Nov 7169 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026145 ms
May 30, 2026157 ms
Jun 6, 2026156 ms
Jun 13, 2026152 ms
Jun 20, 2026155 ms
Jun 27, 2026153 ms
Jul 4, 2026161 ms
Jul 11, 2026155 ms
Jul 18, 2026152 ms
Jul 25, 2026154 ms
Aug 1, 2026156 ms
Aug 8, 2026161 ms
Aug 15, 2026166 ms
Aug 22, 2026176 ms
Aug 29, 2026170 ms
Sep 5, 2026176 ms
Sep 12, 2026180 ms
Sep 19, 2026174 ms
Sep 26, 2026190 ms
Oct 3, 2026187 ms
Oct 10, 2026178 ms
Oct 17, 2026177 ms
Oct 24, 2026165 ms
Oct 31, 2026177 ms
Nov 7, 2026169 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 beachsim.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beachsim.de at 0.4 s0.4 s
  2. beachsim.de at 0.8 s0.8 s
  3. beachsim.de at 1.1 s1.1 s
  4. beachsim.de at 1.5 s1.5 s
  5. beachsim.de at 1.9 s1.9 s
  6. beachsim.de at 2.3 s2.3 s
  7. beachsim.de at 2.6 s2.6 s
  8. beachsim.de at 3.0 s3.0 s

beachsim.de does not allow embedding, so this is Google's rendering of the page.

Speed

2 to fix94
  • Render-blocking requests

    650 ms

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

  • 1,815 HTML elements

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, Judge.me and shop.app), adding 255 KiB and 29 ms of main-thread time.

  • Reduce unused CSS

    23 KiB

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

  • Duplicated JavaScript

    21 KiB

    21 KiB JavaScript is shipped twice across bundles.

  • Use efficient cache lifetimes

    5 KiB

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

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

3 checks passed
  • Mobile performance score: 94

    94/100

    Your mobile performance score is 94. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 441 ms of it running JavaScript. That is comfortably low.

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

2 to fix100
  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BeachSIM hero image of white woman smiling while on mobile …”.

  • 15 images without width and height

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

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

    +15%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

11 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 169 ms

    169 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 729 ms

    729 ms

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

  • Time to Interactive: 3.0 s

    3.0 s

    The page is fully interactive after 3.0 s.

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.006

    0.006

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.48 g

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

4 checks passed
  • Page weight: 1.7 MB in 185 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 185 requests on a phone: other files 896 KiB (85), images 388 KiB (29) and scripts 250 KiB (48). That is a lean page.

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

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

  • 14 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

Google 100100
  • 105 internal links, 4 external

    The homepage links to 105 pages on beachsim.de and 4 external pages.

8 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Reise eSIM und Reise SIM Karte für 160+ Länder, dazu IoT- und GPS-Tracker-SIM-Karten. eSIM sofort per E-Mail, SIM Karte…”.

  • One H1 headline

    Your main headline reads: “Verbindung, wo immer du bist”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Reise eSIM & SIM Karte fürs Ausland | IoT SIM | BeachSIM”.

  • Canonical URL set

    The canonical URL is https://beachsim.de/.

  • Structured data in place

    Structured data found: FAQPage, 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://beachsim.de/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: 4 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,076 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

4 to fix68
  • 1 page without a title

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

  • 3 linked pages hidden from search

    /customer_authentication/redirect, /collections and /collections/all are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

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

  • 1 page without an H1

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

  • 1 page with very little text

    /pages/gps-sim-balance has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    /customer_authentication/redirect took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    61 of 76 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix93
  • 1 broken external link

    1 link to other sites is dead, for example https://app.beachsim.com/4Dih/beachsim-de (404).

  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 1 link through redirect chains

    1 link go through two or more redirects, for example https://beachsim.de/customer_authentication/redirect?locale=de&region_country=DE.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (beachsim.de).

  • Valid certificate (59 days left)

    The certificate from Let's Encrypt · YE1 verifies for beachsim.de and is valid for another 59 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://beachsim.de redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

Domain and trust

  • No CAA record

    beachsim.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

4 to fix50
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • 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 519 words of copy

    The homepage carries about 519 words of visible text.

2 checks passed
  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 123 testimonial or review blocks and 1 customer or partner logo.

Email authentication

2 to fix65
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be beachsim.de is still delivered. Add a report address, check the reports, then move to quarantine.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Email authentication score: 65/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

1 checks passed
  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com include:148893802.spf01.hubspotemail.net -all”.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 10 cookies set on arrival

    10

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

  • 12 other companies contacted

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

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Judge Me Reviews

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

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on beachsim.de, including 4 speed issues and 4 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