Job board software speed test

13 job board platforms, each measured on a live customer board rather than the vendor's marketing site. 0 boards scored 90 or better on mobile. 6 pass their Core Web Vitals assessment and 3 fail it outright.

Kardow makes one of the platforms in this table, which is a reason to check the work rather than to take it on faith. Every row names the board that was tested and links to the PageSpeed screenshot, so any number here can be reproduced in about thirty seconds.

Mobile results

Mobile is the primary number. Google indexes mobile-first, and most job seekers arrive on a phone. Sorted fastest first.

Mobile PageSpeed Insights results by job board platform
Platform Score LCP FCP TBT CLS Speed Index Core Web Vitals
Kardow
85
4.1s 1.2s 150ms 0.005 2.7s Passed
JobKit
85
3.5s 3s 0ms 0 3.3s Passed
Oru
64
7.2s 3.7s 100ms 0 5.4s No field data
Cavuno
58
5.7s 1.4s 830ms 0 3.5s Failed
JobBoard.io
57
10.9s 8.2s 40ms 0 8.2s Passed
Job Board Fire
55
10.6s 5.6s 250ms 0 6.2s Failed
JobBoardHQ
55
15s 4.6s 240ms 0 7.1s Passed
Artha Job Board
54
3.4s 3.2s 1340ms 0.02 7.4s Failed
JBoard
51
7s 1.9s 78ms 0.078 5.2s Passed
Job Boardly
50
6s 2.1s 980ms 0.001 5.7s No field data
Getro
48
4.1s 2.1s 1240ms 0.114 10.8s Passed
Niceboard
43
14.5s 3.6s 730ms 0.116 5.2s No field data
JobBoardSoftware.io
25
28.5s 3.7s 1800ms 0.147 15.2s No field data

Desktop results

Desktop scores are higher across the board and mean less. They are here because a gap between a platform's desktop and mobile numbers usually points at JavaScript weight, which a fast machine hides and a phone does not.

Desktop PageSpeed Insights results by job board platform
Platform Score LCP FCP TBT CLS Speed Index
Kardow
99
0.9s 0.3s 10ms 0.001 0.7s
JobKit
98
0.6s 0.6s 20ms 0.078 0.9s
Oru
97
1.2s 0.7s 10ms 0 0.7s
Job Board Fire
97
1.2s 0.9s 60ms 0.006 0.9s
JobBoard.io
84
0.7s 0.5s 300ms 0.005 1.9s
JobBoardHQ
83
2.7s 0.9s 20ms 0.021 1.5s
JBoard
77
1.4s 0.5s 400ms 0.005 1.4s
Cavuno
72
0.8s 0.3s 750ms 0.012 1.3s
Job Boardly
72
2s 0.6s 350ms 0.039 1.8s
Artha Job Board
67
0.9s 0.9s 910ms 0.013 1.9s
Niceboard
62
2.7s 0.8s 520ms 0.003 1.3s
Getro
59
2s 0.6s 920ms 0.015 2s
JobBoardSoftware.io
22
6.5s 0.8s 1720ms 0.259 4.8s

What was tested, and the evidence

One live board per platform, chosen because it is a real deployment with real listings on it. Each row links to the board and to the PageSpeed screenshot the numbers were read from.

The board tested for each platform, with screenshot evidence
Platform Board tested Tested on Screenshots
Kardow peopleopsjobs.io 2026-06-08 Mobile
JobKit jobs.rubyonrails.org 2026-06-09 Mobile
Oru pge-remotehub.oru.club 2026-06-08 Mobile
Cavuno aviationcareers.com.au 2026-06-08 Mobile
JobBoard.io jobs.cityandstateny.com 2026-06-09 Mobile
Job Board Fire jobs.trellis.net 2026-06-08 Mobile
JobBoardHQ www.jobsindoorcounty.com 2026-06-09 Mobile
Artha Job Board www.edujobsindia.com 2026-06-08 Mobile
JBoard www.mining.com 2026-06-08 Mobile
Job Boardly tradiejobs.com.au 2026-06-08 Mobile
Getro jobs.all-hands.us 2026-06-08 Mobile
Niceboard jobs.forcebrands.com 2026-06-08 Mobile
JobBoardSoftware.io firstnationsjobs.com.au 2026-06-08 Mobile

Methodology

Every score comes from Google PageSpeed Insights at pagespeed.web.dev, run on the Mobile tab and then the Desktop tab, between 2026-06-08 to 2026-06-09. The performance score, LCP, FCP, TBT, CLS and Speed Index are Lighthouse lab measurements. The Core Web Vitals column is different: it is the field-data assessment from the Chrome User Experience Report, which reflects what real visitors experienced over the preceding 28 days, and it is blank where a board does not have enough traffic to produce one.

Each platform was tested against a live job board built on it by a customer. Testing a vendor's marketing homepage would measure a static page with none of the search, filtering or listing volume that makes a job board slow, and every platform would look excellent.

The limitations, stated plainly. Each figure is a single snapshot of a single board, not an average across a fleet, so it carries the run-to-run variance PageSpeed has and the choices that board's operator made about images, fonts, tag managers and chat widgets. Two boards on the same platform can differ by thirty points. Treat a row here as evidence of what a platform tends to produce, and confirm it by running the tested URL yourself.

Re-test cadence: twice a year. Each row carries the date it was last measured, so a stale row is visible rather than implied. Last update 2026-08-30.

Platforms not in this dataset

17 of the 30 platforms in the full comparison have no row above, almost always because no live customer board could be found to test. Several sell to enterprises whose boards sit behind a login. Listing them here rather than quietly dropping them is the point: a missing measurement is not a bad one.

SmartJobBoard Jobbex Boxwood GO (Naylor) Spacewalk JobBoardSoftware.com eJobboard eJobSiteSoftware Careerleaf Madgex Jobiqo WP Job Manager YM Careers Web Scribble Talenetic TrueJob CareerSiteCloud JobMount

Frequently asked questions

How were these job board speed scores measured?

Each platform was measured with Google PageSpeed Insights against a live job board built on it by a real customer, not the platform's own marketing website. That distinction is the whole point of the test: a vendor's homepage is a static marketing page, while the thing you are buying is a job board with search, filters and hundreds of listings on it. Both the Mobile and Desktop tabs were recorded, along with the Core Web Vitals assessment from Chrome field data where enough of it existed. The tests were run 2026-06-08 to 2026-06-09.

Why is only one board tested per platform?

Because a platform does not have one speed, it has a range, and the operator controls part of it. Any board can be slowed down by a heavy hero image, a tag manager, three tracking pixels and an embedded chat widget. A single snapshot of one live board tells you what that platform tends to produce in practice, which is more useful than a vendor benchmark and less reliable than a fleet average. Read the numbers as a signal, not a verdict, and click through to the tested board to see what you are looking at.

Why are some platforms missing from the table?

17 of the 30 platforms in our comparison are not in this table. In most cases we could not find a live customer board to test: the platform sells to enterprises whose boards sit behind a login, or the customers it names publicly have since migrated. Rather than test the vendor's marketing site and present that as a board speed, they are listed as untested below. We would rather have a hole in the dataset than a number that measures the wrong thing.

Does job board speed actually affect rankings?

It affects them, but less than most speed articles imply, and more than most operators assume. Core Web Vitals are a ranking signal in Google search and a tie-breaker rather than a lever: a fast page does not outrank a more relevant slow one. Where speed bites hardest on a job board is crawling and conversion. A board with thousands of listings has a crawl budget, and slow responses mean fewer job pages get crawled per visit, which delays new listings appearing. On the candidate side, a five-second load on mobile is where applications get abandoned. Total Blocking Time is the metric to watch on job boards specifically, because search and filter interfaces tend to ship a lot of JavaScript.

How often is this dataset re-tested?

Twice a year, and the date on each row says when it was last measured. Platforms ship changes and customer boards change hands, so a score from eighteen months ago is not evidence of anything. If a row here is stale by that standard, treat it as unmeasured. We would rather publish a small honest table than a large stale one.

Kardow publishes this table and also appears in it. Why trust it?

You should discount it, and here is what to check. Every row names the exact board that was tested and links to it, and every row links to the PageSpeed screenshot, so any number here can be reproduced in about thirty seconds by running the same URL yourself. The tested Kardow board is a customer board with real traffic and real listings, chosen the same way as the others, not a stripped-down demo. Kardow does not win every metric in this table and the losses are shown rather than omitted.

Where this fits