Website review, no card needed
oysterhr.com website review
Visit site (opens in a new tab)Reviewed 3 November 202626 issues · 77 checks
This review found 26 issues worth fixing on oysterhr.com, 11 of them high impact, across 77 checks. The most urgent: website-files.com adds 1.4 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Oyster
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.3 s |
| May 23, 2026 | 5.4 s |
| May 30, 2026 | 5.6 s |
| Jun 6, 2026 | 5.5 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 388 ms |
| May 23, 2026 | 409 ms |
| May 30, 2026 | 458 ms |
| Jun 6, 2026 | 455 ms |
| Jun 13, 2026 | 418 ms |
| Jun 20, 2026 | 367 ms |
| Jun 27, 2026 | 293 ms |
| Jul 4, 2026 | 291 ms |
| Jul 11, 2026 | 296 ms |
| Jul 18, 2026 | 300 ms |
| Jul 25, 2026 | 294 ms |
| Aug 1, 2026 | 292 ms |
| Aug 8, 2026 | 285 ms |
| Aug 15, 2026 | 285 ms |
| Aug 22, 2026 | 301 ms |
| Aug 29, 2026 | 318 ms |
| Sep 5, 2026 | 327 ms |
| Sep 12, 2026 | 338 ms |
| Sep 19, 2026 | 320 ms |
| Sep 26, 2026 | 303 ms |
| Oct 3, 2026 | 296 ms |
| Oct 10, 2026 | 287 ms |
| Oct 17, 2026 | 288 ms |
| Oct 24, 2026 | 300 ms |
| Oct 31, 2026 | 311 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
How it loaded on a phone
1.1 s
2.2 s
3.2 s
4.3 s
5.4 s
6.5 s
7.6 s
8.7 s
Speed
website-files.com adds 1.4 s
1.4 swebsite-files.com costs a phone 1.4 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.2 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
intellimize.co adds 1.1 s
1.1 sintellimize.co costs a phone 1.1 s of main-thread work and 104 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 10.1 s
A phone's processor spends 10.1 s on main-thread work while loading, 4.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,308 HTML elements
The page has 4,308 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (website-files.com, intellimize.co and Hubspot and others), adding 1.7 MB and 2.9 s of main-thread time.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 558 ms. During a long task the page ignores taps.
Reduce unused JavaScript
441 KiBAbout 441 KiB of JavaScript is downloaded but never used on this page.
Hubspot adds 279 ms
279 msHubspot costs a phone 279 ms of main-thread work and 211 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.
Use efficient cache lifetimes
258 KiB11 files are served with short cache lifetimes, so returning visitors download them again (258 KiB).
Reduce unused CSS
46 KiBAbout 46 KiB of CSS is downloaded but never applied on this page.
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: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 14.0 s
14.0 sThe page becomes fully interactive after 14.0 s. Good is under 3.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 454 ms
454 msReal visitors wait 454 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user TTFB: 581 ms
581 msReal visitors wait 581 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 388 ms to 311 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 41% faster for real visitors
-41%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.3 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.7 s
1.7 sYour largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Scale from the U.S. to everywhere”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image in older formats
1 image (30 KiB) is 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.
About 0.5 g of CO₂ per visit
0.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.55 g of CO₂e: 65.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.9 MB in 82 requests
1.9 MBYour homepage downloads 1.9 MB in 82 requests on a phone: scripts 1.0 MB (43), other files 270 KiB (20) and fonts 236 KiB (2). That is a lean page.
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 images without alt text
3 images have no alt text, which hurts accessibility and image search.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
11 H1 headlines
There are 11 <h1> headlines (“The world is your Oyster”, “Scale from the U.S. to everywhere” and “The employer of record helping Britain hire every…”). One clear main headline is easier for people and search engines.
81 internal links, 26 external
The homepage links to 81 pages on oysterhr.com and 26 external pages.
7 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Hire, pay, and manage teams globally with Oyster. Streamline payroll, ensure compliance, and simplify HR in +180 countr…”.
Title: 65 characters
Your title is a healthy 65 characters: “Oyster HR | Global Payroll & HR Software | Hire in +180 Countries”.
Canonical URL set
The canonical URL is https://www.oysterhr.com/.
Structured data in place
Structured data found: BreadcrumbList and Organization.
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.oysterhr.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,211 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.oysterhr.com/llms.txt (15 KiB, 24 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.oysterhr.com/product/people-partner-services is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 679 words of copy
The homepage carries about 679 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: “Book a Demo”.
14 calls to action
The homepage has 14 calls to action, for example “Pricing”, “Sign Up” and “Book a Demo”.
Social proof on the page
Social proof on the homepage: 14 testimonial or review blocks, 19 customer or partner logos and 10 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 5 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (measured from a US location before any click).
51 other companies contacted
Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Ketch
A consent management tool (Ketch) 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 oysterhr.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
- Webflow
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- Webflow
Hiring
- Hiring
- 24 open roles
- Teams
- Go To Market (7), Operations (7), Product Development (6), Finance (3)
- Job board
- ashby
- Careers page
- www.oysterhr.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on oysterhr.com, including 20 speed issues and 1 SEO issue. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.