www.paycom.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:01 UTC. Grade B (83/100), with the screenshots, the timings and the fixes that matter.

https://www.paycom.com/

20 October 2026 at 14:01 UTC · Free test · report pt_22c4066e2ee6
Grade
B
83/100
Performance89/100
Structure73/100

10 audit(s) passed, 6 need work

First byte (TTFB)410 msmeasured from this server
Fully loaded1.51 sfirst byte + slowest asset
Requests26document + assets
Page weight1.58 MBcompressed transfer
HTML document57.9 KBgzip
ProtocolHTTP/3server not sent
Third-party505.8 KBother hosts

Where the first byte went

  • DNS lookup 61 ms 15%
  • TCP connect 77 ms 19%
  • Server wait 273 ms 67%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 55% of 4,999 pages tested here410 ms against a median of 449 ms
Page weightheavier than 75% of 4,999 pages tested here1.58 MB against a median of 650.3 KB
Fully loadedfaster than 69% of 4,999 pages tested here1.51 s against a median of 1.84 s
Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte arrived in 410 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 1.58 MB over 26 request(s). Images files are 94% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 31% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Images 21 requests
1.48 MB 94%
Javascript 3 requests
40.5 KB 3%
Other 1 request
92 B 0%

Transfer size, compressed as sent. 26 request(s) in total, 1.58 MB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 410 ms. Of that, 273 ms was the server thinking and 138 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Image delivery and format

high impact

4 image(s) over 200 KB and 3 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Render-blocking resources

high impact

6 render-blocking resource(s) in the document head (4 script(s), 2 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

medium impact

The page transfers 1.58 MB across 26 request(s), with the document itself at 57.9 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Third-party weight

medium impact

2 third-party host(s) serve 505.8 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

Waterfall

Slowest requests

IMAGEScdn.paycom.com/mkon/www/media/homepage-content/ESS-Ov…
1.10 s
IMAGESwww.paycom.com/images/home/iwant-tm.svg
1.05 s
IMAGESwww.paycom.com/images/home/iwant-sparkle-Track-Green.svg
1.00 s
IMAGESwww.paycom.com/images/home/Newsweek-US-Online-Platfor…
969 ms
IMAGESwww.paycom.com/images/home/iwant-tm-White.svg
956 ms
IMAGESwww.paycom.com/images/home/accolade-trustradius-buyer…
940 ms
JAVASCRIPTwww.paycom.com/js/data-layer.js
938 ms
IMAGESwww.paycom.com/images/loading.gif
938 ms
JAVASCRIPTwww.paycom.com/js/http-block-tests.js
938 ms
IMAGESwww.paycom.com/images/home/posters/DDX-Poster-Img.png
934 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://cdn.paycom.com/mkon/www/media/homepage-content/ESS-Overlap-Phones.webp 3rd partyimages2001.10 s209.5 KB
https://www.paycom.com/images/home/iwant-tm.svgimages2001.05 s996 B
https://www.paycom.com/images/home/iwant-sparkle-Track-Green.svgimages2001.00 s490 B
https://www.paycom.com/images/home/Newsweek-US-Online-Platforms-2026.pngimages200969 ms63.3 KB
https://www.paycom.com/images/home/iwant-tm-White.svgimages200956 ms1022 B
https://www.paycom.com/images/home/accolade-trustradius-buyers-choice-2026.pngimages200940 ms19.1 KB
https://www.paycom.com/js/data-layer.js?v=1791898193javascript200938 ms5.2 KB
https://www.paycom.com/images/loading.gifimages200938 ms723 B
https://www.paycom.com/js/http-block-tests.jsjavascript200938 ms701 B
https://www.paycom.com/images/home/posters/DDX-Poster-Img.pngimages200934 ms55.6 KB
https://www.paycom.com/js/jquery/jquery-3.7.0.min.jsjavascript200934 ms34.6 KB
https://www.paycom.com/images/home/dedicated-service/professional-client.pngimages200932 ms323.9 KB
https://www.paycom.com/images/home/dedicated-service/support-employee.pngimages200932 ms254.1 KB
https://www.paycom.com/images/home/posters/IWant-Poster-Img.pngimages200930 ms47.6 KB
https://www.paycom.com/images/home/posters/homepage-security-poster.jpegimages200927 ms109.7 KB
https://www.paycom.com/images/home/posters/Gone-Poster-Img.pngimages200927 ms35.6 KB
https://www.paycom.com/images/home/Forrester-Logo-White.svgimages200927 ms1.4 KB
https://www.paycom.com/images/home/accolade-USA-Today-2026.pngimages200911 ms15.2 KB
https://www.paycom.com/images/home/accolades-G2-Leader-Spring-2026.pngimages200907 ms12.7 KB
https://www.paycom.com/images/mobile-app/logo-play-store.svgimages200901 ms1.8 KB
https://www.paycom.com/images/mobile-app/logo-app-store.svgimages200900 ms3.2 KB
https://www.paycom.com/images/home/posters/Payroll-Dashboard-Poster-Img.pngimages200893 ms62.0 KB
https://www.paycom.com/images/home/forrester-logo.svgimages200892 ms2.8 KB
https://play.vidyard.com/JY3gmVfDKPw29ZnMp7ScQq.jpg 3rd partyother302886 ms92 B
https://cdn.paycom.com/mkon/www/media/homepage-content/PHONE-Floating2-ARC-ESS-Home.webp 3rd partyimages200799 ms296.3 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.