Website review, no card needed

teds-place.nl logo

teds-place.nl website review

Visit site (opens in a new tab)Reviewed 25 October 202640 issues · 89 checks

This review found 40 issues worth fixing on teds-place.nl, 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
3.1 s2.6 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.9 s
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20263.0 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.7 s
Aug 8, 20262.6 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
121 ms108 msMay 2Oct 17112 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026114 ms
May 9, 2026113 ms
May 16, 2026112 ms
May 23, 2026112 ms
May 30, 2026112 ms
Jun 6, 2026112 ms
Jun 13, 2026113 ms
Jun 20, 2026114 ms
Jun 27, 2026116 ms
Jul 4, 2026119 ms
Jul 11, 2026119 ms
Jul 18, 2026115 ms
Jul 25, 2026112 ms
Aug 1, 2026110 ms
Aug 8, 2026109 ms
Aug 15, 2026110 ms
Aug 22, 2026110 ms
Aug 29, 2026111 ms
Sep 5, 2026111 ms
Sep 12, 2026111 ms
Sep 19, 2026111 ms
Sep 26, 2026111 ms
Oct 3, 2026112 ms
Oct 10, 2026112 ms
Oct 17, 2026112 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 teds-place.nl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. teds-place.nl at 0.6 s0.6 s
  2. teds-place.nl at 1.2 s1.2 s
  3. teds-place.nl at 1.8 s1.8 s
  4. teds-place.nl at 2.4 s2.4 s
  5. teds-place.nl at 3.0 s3.0 s
  6. teds-place.nl at 3.5 s3.5 s
  7. teds-place.nl at 4.1 s4.1 s
  8. teds-place.nl at 4.7 s4.7 s

Speed

11 to fix38
  • Use efficient cache lifetimes

    2.0 s · 14.9 MB

    61 files are served with short cache lifetimes, so returning visitors download them again (14.9 MB).

  • Render-blocking requests

    2.3 s

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

  • Reduce unused JavaScript

    1.1 s · 738 KiB

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

  • Mobile performance score: 38

    38/100

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

  • Improve image delivery

    3.1 MB

    3 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google Maps and piggy.eu and others), adding 1.4 MB and 593 ms of main-thread time.

  • Google Tag Manager adds 334 ms

    334 ms

    Google Tag Manager costs a phone 334 ms of main-thread work and 703 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 CSS

    300 ms · 79 KiB

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

  • Font display

    350 ms

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

  • Main-thread work: 2.1 s

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

  • Google Maps adds 122 ms

    122 ms

    Google Maps costs a phone 122 ms of main-thread work and 390 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 CSS

    150 ms · 2 KiB

    2 KiB could be saved by minifying CSS.

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    25 KiB

    Polyfills for old browsers add 25 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.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 258 ms

    258 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Real-user CLS: 0.95

    0.95

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Cumulative Layout Shift: 1.103

    1.103

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

  • Time to Interactive: 19.8 s

    19.8 s

    The page becomes fully interactive after 19.8 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 text “YOUR PARTY. OUR PLACE. NO PROBLEM.”.

  • Speed Index: 7.7 s

    7.7 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

2 checks passed
  • Real-user INP: 123 ms

    123 ms

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

  • Total Blocking Time: 127 ms

    127 ms

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

Images and page weight

1 to fix70
  • Page weight: 16.6 MB in 110 requests

    16.6 MB

    Your homepage downloads 16.6 MB in 110 requests on a phone: media 9.9 MB (3), images 4.0 MB (17) and scripts 1.6 MB (37). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

    4 images further down the page (160 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.7 g of CO₂ per visit

    4.71 g

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

8 to fixGoogle 8690
  • 5 text elements with low contrast

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

  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

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

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Teds | All Day Food & Drinks | Enjoy yourself all day & every day.”.

  • 83 internal links, 17 external

    The homepage links to 83 pages on teds-place.nl and 17 external pages.

7 checks passed
  • Meta description: 97 characters

    Your meta description is 97 characters: “Teds isn’t just about breakfast, it’s about good food & drinks and having amazing vibes together.”.

  • One H1 headline

    Your main headline reads: “Brunch isn’t a time of day,it’s a lifestyle”.

  • Canonical URL set

    The canonical URL is https://teds-place.nl/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and Restaurant.

  • 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://teds-place.nl/sitemap_index.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.

  • No llms.txt

    There is no https://teds-place.nl/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.

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.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without a meta description

    https://teds-place.nl/locations/amsterdam-de-pijp, https://teds-place.nl/locations/amsterdam-oud-west and https://teds-place.nl/locations/breda-botanique have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://teds-place.nl/specials, https://teds-place.nl/specials/afternoon-t and https://teds-place.nl/events took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 9687
  • 4 small tap targets

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

  • 3 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 541 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP” and “Book your table.”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop”, “Book your table.” and “Order now”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 teds-place.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager

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 teds-place.nl, including 22 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