Website review, no card needed

smartr.me logo

smartr.me website review

Visit site (opens in a new tab)Reviewed 29 October 202637 issues · 84 checks

This review found 37 issues worth fixing on smartr.me, 13 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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.7 s3.1 sMay 9Oct 243.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.6 s
May 16, 20263.6 s
May 23, 20263.6 s
May 30, 20263.6 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Oct 24, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
171 ms134 msMay 9Oct 24144 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026167 ms
May 16, 2026163 ms
May 23, 2026156 ms
May 30, 2026152 ms
Jun 6, 2026146 ms
Jun 13, 2026144 ms
Jun 20, 2026143 ms
Jun 27, 2026142 ms
Jul 4, 2026143 ms
Jul 11, 2026140 ms
Jul 18, 2026140 ms
Jul 25, 2026139 ms
Aug 1, 2026138 ms
Aug 8, 2026138 ms
Aug 15, 2026138 ms
Aug 22, 2026138 ms
Aug 29, 2026138 ms
Sep 5, 2026141 ms
Sep 12, 2026144 ms
Sep 19, 2026145 ms
Sep 26, 2026146 ms
Oct 3, 2026146 ms
Oct 10, 2026145 ms
Oct 17, 2026145 ms
Oct 24, 2026144 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 smartr.me (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. smartr.me at 0.4 s0.4 s
  2. smartr.me at 0.8 s0.8 s
  3. smartr.me at 1.2 s1.2 s
  4. smartr.me at 1.6 s1.6 s
  5. smartr.me at 1.9 s1.9 s
  6. smartr.me at 2.3 s2.3 s
  7. smartr.me at 2.7 s2.7 s
  8. smartr.me at 3.1 s3.1 s

Speed

11 to fix43
  • Render-blocking requests

    6.2 s

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

  • Reduce unused JavaScript

    4.2 s · 606 KiB

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

  • Use efficient cache lifetimes

    3.1 s · 517 KiB

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

  • Mobile performance score: 43

    43/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Wistia and consentmanager.net and others), adding 1.2 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    670 ms · 167 KiB

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

  • Google Tag Manager adds 445 ms

    445 ms

    Google Tag Manager costs a phone 445 ms of main-thread work and 536 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: 3.4 s

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

  • Wistia adds 287 ms

    287 ms

    Wistia costs a phone 287 ms of main-thread work and 367 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 JavaScript

    300 ms · 22 KiB

    22 KiB could be saved by minifying JavaScript.

  • 13 long tasks on the main thread

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

  • Improve image delivery

    250 ms · 157 KiB

    3 images could be 157 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 45 KiB

    Polyfills for old browsers add 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    150 ms · 26 KiB

    26 KiB could be saved by minifying CSS.

  • Font display

    150 ms

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

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

    4 ms

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

Core Web Vitals

12 to fix0
  • 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.32

    0.32

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

  • First Contentful Paint: 11.5 s

    11.5 s

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

  • Largest Contentful Paint: 20.3 s

    20.3 s

    Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Collage of UI cards showing a profile, hiring progress, ana…”.

  • Time to Interactive: 20.6 s

    20.6 s

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

  • Speed Index: 11.5 s

    11.5 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user INP: 203 ms

    203 ms

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 934 ms

    934 ms

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

  • Total Blocking Time: 498 ms

    498 ms

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

  • 34 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

2 checks passed
  • Tap response (INP) got 12% faster for real visitors

    -12%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 2.9 MB in 129 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 129 requests on a phone: scripts 1.5 MB (46), fonts 895 KiB (17) and images 259 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    75 KiB

    2 images are downloaded at several times the size a phone draws them, for example SR-SAP-Hero-2026.png at 1,454 px wide, shown at 256 px. Resized copies would save about 75 KiB.

  • 3 images in older formats

    3 images (168 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.

  • 1 image below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.82 g

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

Accessibility

6 to fixGoogle 8792
  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

  • 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 (17 elements)

    All page content should be contained by landmarks: 17 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 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 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 8598
  • 7 links crawlers can't follow

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

  • 118 internal links, 17 external

    The homepage links to 118 pages on smartr.me and 17 external pages.

8 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Enterprise-grade AI hiring platform designed for HR and recruiting talent. SmartRecruiters all-in-one solution, so you …”.

  • One H1 headline

    Your main headline reads: “AI-Powered Hiring Platform That Delivers Results”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Talent Acquisition and Hiring Platform - AI-Powered”.

  • Canonical URL set

    The canonical URL is https://www.smartrecruiters.com/.

  • Structured data in place

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

  • 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://www.smartrecruiters.com/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.smartrecruiters.com/llms.txt (195 KiB, 838 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.smartrecruiters.com/product-preview is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.smartrecruiters.com/product-preview has 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 75 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 701 words of copy

    The homepage carries about 701 words of visible text.

4 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Pricing”, “Get started” and “Learn more →”.

  • 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: 6 testimonial or review blocks, 21 customer or partner logos and “over 4,000 customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 cookies set on arrival

    17

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

  • 48 other companies contacted

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

1 checks passed
  • Consent tool: consentmanager

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

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 smartr.me, 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
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on smartr.me, including 23 speed issues, 1 SEO issue and 2 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