Website review, no card needed
tracker-rms.com website review
Visit site (opens in a new tab)Reviewed 23 October 202631 issues · 84 checks
This review found 31 issues worth fixing on tracker-rms.com, 17 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80B- #46,289 of 117,615 reviewed websitesbeats 55%
- #30,852 of 66,923 online storesbeats 47%
- #618 of 2,700 WooCommerce storesbeats 73%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 151 ms |
| May 9, 2026 | 157 ms |
| May 16, 2026 | 142 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 135 ms |
| Jun 6, 2026 | 123 ms |
| Jun 13, 2026 | 135 ms |
| Jun 20, 2026 | 135 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 124 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 115 ms |
| Aug 8, 2026 | 115 ms |
| Aug 15, 2026 | 115 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 113 ms |
| Sep 26, 2026 | 124 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 90 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
0.9 s
1.9 s
2.8 s
3.8 s
4.7 s
5.7 s
6.6 s
7.6 s
Speed
Reduce unused JavaScript
4.3 s · 955 KiBAbout 955 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Render-blocking requests
2.5 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Use efficient cache lifetimes
1.1 s · 171 KiB10 files are served with short cache lifetimes, so returning visitors download them again (171 KiB).
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 73). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.2 s
A phone's processor spends 7.2 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,472 HTML elements
The page has 5,472 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 (Google Tag Manager, YouTube and cloudfront.net and others), adding 2.2 MB and 1.8 s of main-thread time.
Reduce unused CSS
750 ms · 180 KiBAbout 180 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 746 ms
746 msGoogle Tag Manager costs a phone 746 ms of main-thread work and 994 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.
Improve image delivery
150 ms · 348 KiB10 images could be 348 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
YouTube adds 397 ms
397 msYouTube costs a phone 397 ms of main-thread work and 971 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 261 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 32 KiB32 KiB could be saved by minifying JavaScript.
Legacy JavaScript
150 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 73 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.1 s
9.1 sThe first text or image appears after 9.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 21.3 s
21.3 sYour largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tracker holds every part of the recruitment business in one…”.
Time to Interactive: 23.5 s
23.5 sThe page becomes fully interactive after 23.5 s. Good is under 3.8 s.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 771 ms
771 msScripts block taps and scrolling for 771 ms in total while the page loads. Good is under 200 ms.
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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 363 ms
363 msReal visitors wait 363 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 151 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 197 requests
5.3 MBYour homepage downloads 5.3 MB in 197 requests on a phone: scripts 2.4 MB (60), images 2.2 MB (75) and fonts 362 KiB (10). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (30 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.49 g of CO₂e: 179.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
64 text elements with low contrast
64 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (3 elements)
Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 177 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Staffing & Recruitment Software | ATS & CRM for Agencies | Tracker”.
137 internal links, 5 external
The homepage links to 137 pages on tracker-rms.com and 5 external pages.
7 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Tracker is the all-in-one ATS & CRM for staffing and recruitment agencies. AI sourcing, sales automation, and back offi…”.
One H1 headline
Your main headline reads: “Because Tracker handles everything that isn’t.”.
Canonical URL set
The canonical URL is https://www.tracker-rms.com/.
Structured data in place
Structured data found: 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.tracker-rms.com/sitemaps.xml.
AI search readiness
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.
3 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 (8,305 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.tracker-rms.com/llms.txt (2 KiB, 5 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
7 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.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187044603&tm=gtm002&Ver=2&mid=a3c98a83-c790-4170-b628-587c8db38516&bo=1&sid=a8388060cecb11f191f3516c8dfb9ee3&vid=a8387cb0cecb11f194380ba0c048b412&vids=1&msclkid=N&pi=9.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 small tap targets
3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 12-field form
Your longest form asks for 12 fields (9 required). Every extra field lowers completion.
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.
About 6,707 words of copy
The homepage carries about 6,707 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” and “View Pricing”.
16 calls to action
The homepage has 16 calls to action, for example “Book a demo”, “Plans & Pricing” and “Services & contact”.
Social proof on the page
Social proof on the homepage: 181 testimonial or review blocks, 7 customer or partner logos, a star rating and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
24 cookies set on arrival
24Opening the homepage sets 24 cookies, 1 of them by other companies (measured from a US location before any click).
33 other companies contacted
Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 tracker-rms.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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on tracker-rms.com, including 17 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.