Website review, no card needed

exponenthr.com logo

exponenthr.com website review

Visit site (opens in a new tab)Reviewed 11 October 202627 issues · 94 checks

This review found 27 issues worth fixing on exponenthr.com, 8 of them high impact, across 94 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
831 ms729 msApr 18Oct 3794 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026819 ms
Apr 25, 2026813 ms
May 2, 2026798 ms
May 9, 2026757 ms
May 16, 2026748 ms
May 23, 2026741 ms
May 30, 2026742 ms
Jun 6, 2026747 ms
Jun 13, 2026754 ms
Jun 20, 2026764 ms
Jun 27, 2026777 ms
Jul 4, 2026805 ms
Jul 11, 2026789 ms
Jul 18, 2026803 ms
Jul 25, 2026809 ms
Aug 1, 2026781 ms
Aug 8, 2026788 ms
Aug 15, 2026788 ms
Aug 22, 2026779 ms
Aug 29, 2026788 ms
Sep 5, 2026778 ms
Sep 12, 2026772 ms
Sep 19, 2026772 ms
Sep 26, 2026786 ms
Oct 3, 2026794 ms
Real-visitor tap response (INP)75th percentile, phones
80 ms69 msApr 18Oct 375 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202673 ms
Apr 25, 202672 ms
May 2, 202672 ms
May 9, 202672 ms
May 16, 202672 ms
May 23, 202672 ms
May 30, 202672 ms
Jun 6, 202672 ms
Jun 13, 202672 ms
Jun 20, 202672 ms
Jun 27, 202672 ms
Jul 4, 202673 ms
Jul 11, 202672 ms
Jul 18, 202671 ms
Jul 25, 202671 ms
Aug 1, 202670 ms
Aug 8, 202670 ms
Aug 15, 202671 ms
Aug 22, 202672 ms
Aug 29, 202672 ms
Sep 5, 202674 ms
Sep 12, 202678 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202675 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

Live view · interaction off

Speed

5 to fix66
  • Use efficient cache lifetimes

    12.8 s · 2.7 MB

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

  • Render-blocking requests

    2.6 s

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

  • Mobile performance score: 66

    66/100

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

  • Reduce unused JavaScript

    450 ms · 72 KiB

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

  • Reduce unused CSS

    300 ms · 65 KiB

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

  • Minify CSS

    150 ms · 25 KiB

    25 KiB could be saved by minifying CSS.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Google Fonts and others), adding 290 KiB and 121 ms of main-thread time.

  • 3 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 0.4 s

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

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 18.0 s

    18.0 s

    Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “STOP SETTLING. THERE’S A BETTER WAY. Do you dread the Open …”.

  • Time to Interactive: 18.0 s

    18.0 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 73 ms to 75 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-03, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 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.1 s

    1.1 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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.1 s

    1.1 s

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

  • Real-user TTFB: 367 ms

    367 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 36 ms

    36 ms

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

Images and page weight

2 to fix70
  • 1 image over 500 KB

    single-source-data-ats-0430.svg weighs 2.4 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.0 MB in 34 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 34 requests on a phone: images 2.5 MB (9), scripts 239 KiB (6) and fonts 91 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.84 g

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

3 to fixGoogle 9195
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • 4 links without text

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

2 to fixGoogle 8594
  • No robots.txt

    There is no robots.txt at exponenthr.com/robots.txt, the first file search crawlers ask for.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 44 internal links, 4 external

    The homepage links to 44 pages on exponenthr.com and 4 external pages.

7 checks passed
  • Meta description: 90 characters

    Your meta description is 90 characters: “ExponentHR delivers a better HR experience for you, your employees, and your organization.”.

  • One H1 headline

    Your main headline reads: “The HR experience you can’t buy anywhere else.”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “The HR experience you can't buy anywhere else”.

  • Canonical URL set

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

  • Structured data in place

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

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

AI search readiness

100
  • No llms.txt

    There is no /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
  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    /resources declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and /resources all use the title “The HR experience you can't buy anywhere else”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    /privacy has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    /privacy has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    /privacy has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.exponenthr.com/media/themes/exponent-hr-2024/assets/font/Corbel.woff2' from origin 'http…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix90
  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • Short HSTS lifetime

    HSTS is set, but max-age is 186 days; one year is the recommended minimum.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • 2 links through redirect chains

    2 links go through two or more redirects, for example https://www.exponenthr.com/privacy.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

4 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (exponenthr.com).

  • Valid certificate (111 days left)

    The certificate from DigiCert Inc · DigiCert EV RSA CA G2 verifies for exponenthr.com and is valid for another 111 days.

  • http:// redirects to https

    http://exponenthr.com redirects to the secure version.

  • All 21 links work

    All 21 links checked from your homepage (17 internal, 4 external) answered without errors.

Domain and trust

  • No CAA record

    exponenthr.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    exponenthr.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 24 years old

    24 years

    exponenthr.com was registered in Nov 2001 through Network Solutions, LLC. An established domain carries more trust with email providers and search engines.

  • Registered until Nov 2033

    exponenthr.com is registered until Nov 2033.

Content and conversion

2 to fix83
  • Thin social proof

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

  • Only about 244 words

    The homepage has only about 244 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “LEARN MORE”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Demo”, “Contact” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Email authentication

100
  • Email authentication score: 100/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 ip4:66.18.8.128/25 ip4:38.67.14.0/26 ip4:206.25.247.155 include:spf.protection.outlook.com include:aspmx.pardot.…”.

  • DKIM signing found

    A DKIM key is published (selector “selector1” and “selector2”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 6 cookies set on arrival

    6

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

  • 5 other companies contacted

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This free review found 27 issues on exponenthr.com, including 10 speed issues, 2 SEO issues 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