Website review, no card needed

corecruitment.com logo

corecruitment.com website review

Visit site (opens in a new tab)Reviewed 18 October 202633 issues · 80 checks

This review found 33 issues worth fixing on corecruitment.com, 12 of them high impact, across 80 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
2.8 s2.4 sApr 25Oct 102.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.6 s
May 2, 20262.6 s
May 9, 20262.4 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
114 ms107 msApr 25Oct 10109 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026113 ms
May 2, 2026112 ms
May 9, 2026110 ms
May 16, 2026111 ms
May 23, 2026110 ms
May 30, 2026110 ms
Jun 6, 2026112 ms
Jun 13, 2026111 ms
Jun 20, 2026112 ms
Jun 27, 2026112 ms
Jul 4, 2026111 ms
Jul 11, 2026109 ms
Jul 18, 2026108 ms
Jul 25, 2026111 ms
Aug 1, 2026111 ms
Aug 8, 2026111 ms
Aug 15, 2026111 ms
Aug 22, 2026108 ms
Aug 29, 2026109 ms
Sep 5, 2026109 ms
Sep 12, 2026109 ms
Sep 19, 2026110 ms
Sep 26, 2026110 ms
Oct 3, 2026109 ms
Oct 10, 2026109 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 corecruitment.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. corecruitment.com at 0.5 s0.5 s
  2. corecruitment.com at 1.0 s1.0 s
  3. corecruitment.com at 1.5 s1.5 s
  4. corecruitment.com at 2.0 s2.0 s
  5. corecruitment.com at 2.5 s2.5 s
  6. corecruitment.com at 3.1 s3.1 s
  7. corecruitment.com at 3.6 s3.6 s
  8. corecruitment.com at 4.1 s4.1 s

Speed

7 to fix62
  • Use efficient cache lifetimes

    1.2 s · 57.9 MB

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

  • Render-blocking requests

    2.3 s

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

  • Reduce unused CSS

    900 ms · 115 KiB

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 85). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 223 KiB

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

  • Font display

    700 ms

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

  • Improve image delivery

    401 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, zi-scripts.com and Google Fonts and others), adding 332 KiB and 216 ms of main-thread time.

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

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

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The international hospitality, leisure, facilities, IT & FM…”.

  • Time to Interactive: 9.1 s

    9.1 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

    The first text or image appears after 3.2 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.0 s

    2.0 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

4 checks passed
  • Real-user INP: 98 ms

    98 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Total Blocking Time: 173 ms

    173 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix55
  • Page weight: 60.0 MB in 68 requests

    60.0 MB

    Your homepage downloads 60.0 MB in 68 requests on a phone: media 57.5 MB (4), images 1.5 MB (47) and scripts 431 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    logo.svg weighs 540 KiB. On a phone connection a single image that size takes seconds.

  • About 17.0 g of CO₂ per visit

    17.01 g

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

3 checks passed
  • 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

5 to fixGoogle 8289
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 8 text elements with low contrast

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

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

    All page content should be contained by landmarks: 10 elements on the page fail 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.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

4 to fixGoogle 10084
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (183 characters)

    Your meta description is 183 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), 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.

  • 120 internal links, 5 external

    The homepage links to 120 pages on corecruitment.com and 5 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “The international hospitality, leisure, facilities, IT & FMCG recruitment agency”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “International hospitality recruitment specialists | COREcruitment”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.corecruitment.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.corecruitment.com/vacancies, https://www.corecruitment.com/candidates/submit-cv, https://www.corecruitment.com/employers/submit-vacancy, https://www.corecruitment.com/candidates, https://www.corecruitment.com/candidates/sectors/chefs and https://www.corecruitment.com/candidates/sectors/fmcg and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 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 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 10087
  • 9 small tap targets

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

  • 1 JavaScript error while loading

    1 error was 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

1 to fix90
  • Thin social proof

    Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No form on the homepage

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

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

    The homepage carries about 318 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request Yours Today”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Download CV Template”, “Sign Up To Our Mailing List” and “Request A Callback”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 7 email links.

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.

  • 5 cookies set on arrival

    5

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 corecruitment.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 Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on corecruitment.com, including 16 speed issues, 4 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