Website review, no card needed

diamir.de logo

diamir.de website review

Visit site (opens in a new tab)Reviewed 22 October 202620 issues · 74 checks

This review found 20 issues worth fixing on diamir.de, 9 of them high impact, across 74 checks. The most urgent: mobile performance score: 46. 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.6 s1.3 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
171 ms139 msMay 2Oct 17167 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026146 ms
May 9, 2026147 ms
May 16, 2026145 ms
May 23, 2026143 ms
May 30, 2026144 ms
Jun 6, 2026148 ms
Jun 13, 2026154 ms
Jun 20, 2026159 ms
Jun 27, 2026162 ms
Jul 4, 2026162 ms
Jul 11, 2026160 ms
Jul 18, 2026156 ms
Jul 25, 2026153 ms
Aug 1, 2026152 ms
Aug 8, 2026151 ms
Aug 15, 2026153 ms
Aug 22, 2026154 ms
Aug 29, 2026154 ms
Sep 5, 2026154 ms
Sep 12, 2026154 ms
Sep 19, 2026154 ms
Sep 26, 2026156 ms
Oct 3, 2026160 ms
Oct 10, 2026163 ms
Oct 17, 2026167 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 diamir.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. diamir.de at 0.5 s0.5 s
  2. diamir.de at 1.1 s1.1 s
  3. diamir.de at 1.6 s1.6 s
  4. diamir.de at 2.2 s2.2 s
  5. diamir.de at 2.7 s2.7 s
  6. diamir.de at 3.2 s3.2 s
  7. diamir.de at 3.8 s3.8 s
  8. diamir.de at 4.3 s4.3 s

Speed

6 to fix46
  • Mobile performance score: 46

    46/100

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

  • Reduce unused JavaScript

    900 ms · 230 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (consentmanager.net and api.video), adding 5.3 MB and 129 ms of main-thread time.

  • api.video adds 0 ms

    0 ms

    api.video costs a phone 0 ms of main-thread work and 5.2 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.

  • Reduce unused CSS

    300 ms · 53 KiB

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

  • 2,156 HTML elements

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

  • Render-blocking requests

    250 ms

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

  • Improve image delivery

    99 KiB

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

  • 1 long task on the main thread

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

  • Use efficient cache lifetimes

    48 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 72 but mobile only 46. A gap that wide usually means heavy scripts and images that hit phones hardest.

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 7.5 s

    7.5 s

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

  • Cumulative Layout Shift: 0.377

    0.377

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Time to Interactive: 8.4 s

    8.4 s

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

  • Speed Index: 6.0 s

    6.0 s

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

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

    +13%

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

  • Largest content (LCP) got 15% slower for real visitors

    +15%

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

7 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.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 INP: 144 ms

    144 ms

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

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

    1.0 s

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

  • Real-user TTFB: 467 ms

    467 ms

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

  • Total Blocking Time: 4 ms

    4 ms

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

Images and page weight

2 to fix64
  • Page weight: 9.3 MB in 86 requests

    9.3 MB

    Your homepage downloads 9.3 MB in 86 requests on a phone: media 5.9 MB (2), images 2.1 MB (56) and fonts 668 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • 1 image in older formats

    1 image (48 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 2.6 g of CO₂ per visit

    2.63 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

1 to fixGoogle 10099
  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 513 internal links, 4 external

    The homepage links to 513 pages on diamir.de and 4 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Ihre Traumreise? Haben wir! ▲ Kleingruppenreisen & individuelle Touren in über 150 Länder ▲ erfahrene Guides & erprobte…”.

  • One H1 headline

    Your main headline reads: “Ihre Traumreise? Haben wir!”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “DIAMIR ▲ Erlebnisreisen & Rundreisen weltweit | DIAMIR”.

  • Canonical URL set

    The canonical URL is https://www.diamir.de/.

  • Structured data in place

    Structured data found: ItemList, Organization, WebPage and WebSite.

  • 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://www.diamir.de/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.diamir.de/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 2 pages slow to respond

    https://www.diamir.de/argentinien and https://www.diamir.de/armenien took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

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

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

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

  • 2 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 644 words of copy

    The homepage carries about 644 words of visible text.

3 checks passed
  • 2 short forms

    2 short forms (3 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.

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 3 other companies contacted

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

2 checks passed
  • Consent tool: consentmanager

    A consent management tool (consentmanager) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 diamir.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager

Company

Founded
2000
Headquarters
Dresden

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on diamir.de, including 11 speed issues, 1 SEO issue and 3 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