Website review, no card needed

nobelrecruitment.com logo

nobelrecruitment.com website review

Visit site (opens in a new tab)Reviewed 7 November 202635 issues · 76 checks

This review found 35 issues worth fixing on nobelrecruitment.com, 12 of them high impact, across 76 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
4.2 s2.1 sAug 1Oct 243.5 s
Show as table
DateReal-visitor load time (LCP)
Aug 1, 20262.5 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Sep 26, 20263.6 s
Oct 3, 20263.9 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Oct 24, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
280 ms108 msAug 1Oct 17260 ms
Show as table
DateReal-visitor tap response (INP)
Aug 1, 2026128 ms
Aug 8, 2026130 ms
Aug 15, 2026129 ms
Sep 26, 2026208 ms
Oct 3, 2026231 ms
Oct 10, 2026246 ms
Oct 17, 2026260 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 nobelrecruitment.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nobelrecruitment.com at 0.5 s0.5 s
  2. nobelrecruitment.com at 1.1 s1.1 s
  3. nobelrecruitment.com at 1.6 s1.6 s
  4. nobelrecruitment.com at 2.2 s2.2 s
  5. nobelrecruitment.com at 2.7 s2.7 s
  6. nobelrecruitment.com at 3.3 s3.3 s
  7. nobelrecruitment.com at 3.8 s3.8 s
  8. nobelrecruitment.com at 4.3 s4.3 s

Speed

8 to fix57
  • Use efficient cache lifetimes

    1.2 s · 6.7 MB

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

  • Reduce unused JavaScript

    1.1 s · 305 KiB

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

  • Render-blocking requests

    1.3 s

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

  • Improve image delivery

    6.0 MB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and JSDelivr CDN and others), adding 989 KiB and 786 ms of main-thread time.

  • Google Tag Manager adds 494 ms

    494 ms

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

  • Main-thread work: 2.1 s

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

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 197 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).

  • Reduce unused CSS

    34 KiB

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

  • Legacy JavaScript

    13 KiB

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

  • 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: 216 ms

    216 ms

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

Core Web Vitals

8 to fix56
  • Largest Contentful Paint: 8.5 s

    8.5 s

    Your largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We headhunt senior GTM talent for B2B tech companies across…”.

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

  • Time to Interactive: 10.0 s

    10.0 s

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

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

    +96%

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

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

    +52%

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

  • Total Blocking Time: 365 ms

    365 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 3 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.078

    0.078

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

Images and page weight

5 to fix18
  • Page weight: 9.1 MB in 82 requests

    9.1 MB

    Your homepage downloads 9.1 MB in 82 requests on a phone: images 6.3 MB (41), other files 1.4 MB (15) and scripts 925 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 5.1 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    5.1 MB

    5 images are downloaded at several times the size a phone draws them, for example Marc-slider.png.jpg at 9,343 px wide, shown at 326 px. Resized copies would save about 5.1 MB.

  • 6 images in older formats

    6 images (5.7 MB) 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.

  • 1 image below the first screen load straight away

    1 image further down the page (849 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.6 g of CO₂ per visit

    2.58 g

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

Accessibility

5 to fixGoogle 9093
  • 7 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

  • 5 links without text

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

  • 4 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 85 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10087
  • Meta description is short (4 characters)

    Your meta description is only 4 characters: “Home”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“We headhunt senior GTM talent for B2B tech compan…” and “Eager to connect with Europe's leading pool of pa…”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 55 internal links, 9 external

    The homepage links to 55 pages on nobelrecruitment.com and 9 external pages.

5 checks passed
  • Title: 53 characters

    Your title is a healthy 53 characters: “SaaS Recruitment Agency Amsterdam - Nobel Recruitment”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://nobelrecruitment.com/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://nobelrecruitment.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.

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 (1,906 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 1 page without a meta description

    https://nobelrecruitment.com/case/case-study-chargebee has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://nobelrecruitment.com/news and https://nobelrecruitment.com/blog use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://nobelrecruitment.com/podcasts and https://nobelrecruitment.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://nobelrecruitment.com/gtm-talent-search, https://nobelrecruitment.com/about-us, https://nobelrecruitment.com/cases, https://nobelrecruitment.com/blog, https://nobelrecruitment.com/contact and https://nobelrecruitment.com/talent and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix86
  • 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.

  • About 1,439 words of copy

    The homepage carries about 1,439 words of visible text.

6 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Get in contact”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 95 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 8 cookies set on arrival

    8

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 nobelrecruitment.com, 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
Hosting
Cyso Group B.V.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on nobelrecruitment.com, including 16 speed issues, 3 SEO issues and 1 conversion gap. 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