Website review, no card needed

asadventure.com logo

asadventure.com website review

Visit site (opens in a new tab)Reviewed 7 November 202642 issues · 85 checks

This review found 42 issues worth fixing on asadventure.com, 13 of them high impact, across 85 checks. The most urgent: improve image delivery. 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.3 s918 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026992 ms
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 2026996 ms
Jul 4, 2026967 ms
Jul 11, 2026957 ms
Jul 18, 2026957 ms
Jul 25, 2026979 ms
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
267 ms215 msMay 16Oct 31221 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026241 ms
May 23, 2026240 ms
May 30, 2026242 ms
Jun 6, 2026245 ms
Jun 13, 2026251 ms
Jun 20, 2026254 ms
Jun 27, 2026258 ms
Jul 4, 2026260 ms
Jul 11, 2026261 ms
Jul 18, 2026260 ms
Jul 25, 2026257 ms
Aug 1, 2026256 ms
Aug 8, 2026258 ms
Aug 15, 2026260 ms
Aug 22, 2026261 ms
Aug 29, 2026259 ms
Sep 5, 2026255 ms
Sep 12, 2026251 ms
Sep 19, 2026246 ms
Sep 26, 2026243 ms
Oct 3, 2026237 ms
Oct 10, 2026229 ms
Oct 17, 2026226 ms
Oct 24, 2026221 ms
Oct 31, 2026221 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 asadventure.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix35
  • Improve image delivery

    4.8 s · 1.1 MB

    20 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.8 s faster on a phone.

  • Reduce unused JavaScript

    3.8 s · 786 KiB

    About 786 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

  • Use efficient cache lifetimes

    2.1 s · 427 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Reduce unused CSS

    750 ms · 103 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Adobe Tag Manager and adn.cloud and others), adding 938 KiB and 676 ms of main-thread time.

  • Render-blocking requests

    750 ms

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

  • Google Tag Manager adds 448 ms

    448 ms

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

  • 2,638 HTML elements

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

  • Main-thread work: 2.4 s

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

  • 9 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    15 KiB

    Polyfills for old browsers add 15 KiB JavaScript that modern phones do not need.

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

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 18.2 s

    18.2 s

    Your largest element takes 18.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: 19.8 s

    19.8 s

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

  • Cumulative Layout Shift: 0.614

    0.614

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

  • Speed Index: 5.6 s

    5.6 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Total Blocking Time: 354 ms

    354 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

6 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.4 s

    1.4 s

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

  • Real-user INP: 181 ms

    181 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 304 ms

    304 ms

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

Images and page weight

4 to fix58
  • Page weight: 3.6 MB in 132 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 132 requests on a phone: scripts 1.7 MB (71), images 1.5 MB (24) and HTML 130 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    [email protected] 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).

  • 3 images far larger than shown

    466 KiB

    3 images are downloaded at several times the size a phone draws them, for example default.png at 840 px wide, shown at 62 px. Resized copies would save about 466 KiB.

  • 3 images in older formats

    3 images (600 KiB) are 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 1.0 g of CO₂ per visit

    1.03 g

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

Accessibility

6 to fixGoogle 8290
  • [role="img"] and [role="image"] elements must have alternative text (12 elements)

    [role="img"] and [role="image"] elements must have alternative text: 12 elements on the page fail this check, rated serious by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (2 elements)

    ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

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

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

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

  • Zoom is disabled

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

  • 1 link without text

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

1 checks passed
  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 6 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 8581
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 2 problems

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

  • No social preview image

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

  • 13 links crawlers can't follow

    13 links have no real href, so search engines can't follow them.

  • 252 internal links, 4 external

    The homepage links to 252 pages on asadventure.com and 4 external pages.

5 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Avontuurlijk aangelegd? Trek naar A.S.Adventure voor onze outdoor -en fashioncollecties ✓ Keuze uit verschillende topme…”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Adventure is everywhere | A.S.Adventure”.

  • Canonical URL set

    The canonical URL is https://www.asadventure.com/nl.html.

  • 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.asadventure.com/sitemap/index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.asadventure.com/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,094 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://www.asadventure.com/nl/verlanglijstje.html and https://www.asadventure.com/nl/c/promoties.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.asadventure.com/nl/asa/services.html and https://www.asadventure.com/nl/verlanglijstje.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.asadventure.com/nl/winkels.html and https://www.asadventure.com/nl/verlanglijstje.html 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 152 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=5487812&tm=gtm002&Ver=2&mid=07ba67fb-ce21-40d2-8944-2628a1adf570&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Adventure%20is%20everywhere%20%7C%20A.S.Advent.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • About 724 words of copy

    The homepage carries about 724 words of visible text.

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop nu” and “Contact”.

  • 2 short forms

    2 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, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 11 cookies set on arrival

    11

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

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on asadventure.com, including 17 speed issues, 4 SEO 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