Tools & Wizards About Us
onpay.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

onpay.com

OnPay | Online Payroll Services, HR and More

Page Load Speed

6.4 sec in total

First Response

144 ms

Resources Loaded

1.1 sec

Page Rendered

5.2 sec

onpay.com screenshot

About Website

Welcome to onpay.com homepage info - get ready to check On Pay best content for United States right away, or after learning these important things about onpay.com

Simplify your payroll services, taxes, HR and benefits. OnPay’s top-rated online payroll services bring it all together.

Visit onpay.com

Key Findings

We analyzed Onpay.com page load time and found that the first response time was 144 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

onpay.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

28/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value3,040 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.28

43/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

onpay.com

144 ms

onpay.com

115 ms

gtm.js

83 ms

A2063326-7af5-41e6-a113-b672d57a2fcb1.js

84 ms

Home

620 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 44% of them (29 requests) were addressed to the original Onpay.com, 27% (18 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Fast.wistia.com. The less responsive or slowest element that took the longest time to load (620 ms) relates to the external source Track.cbdatatracker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 265.5 kB (11%)

Content Size

2.5 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onpay.com main page is 2.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 140.8 kB

  • Original 165.8 kB
  • After minification 152.4 kB
  • After compression 25.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 140.8 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 1.8 kB

  • Original 1.5 MB
  • After minification 1.5 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. On Pay images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 117.4 kB

  • Original 711.4 kB
  • After minification 711.4 kB
  • After compression 594.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 117.4 kB or 16% of the original size.

CSS Optimization

-4%

Potential reduce by 5.5 kB

  • Original 143.3 kB
  • After minification 143.2 kB
  • After compression 137.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Onpay.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (72%)

Requests Now

43

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of On Pay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

onpay.com

onpay.com

144 ms

onpay.com

onpay.com

115 ms

gtm.js

gtm.js

83 ms

A2063326-7af5-41e6-a113-b672d57a2fcb1.js

A2063326-7af5-41e6-a113-b672d57a2fcb1.js

84 ms

Home

Home

620 ms

style.min.css

style.min.css

30 ms

style.css

style.css

35 ms

dashicons.min.css

dashicons.min.css

41 ms

genericons.css

genericons.css

40 ms

all.min.css

all.min.css

46 ms

style.css

style.css

50 ms

onpay-common.css

onpay-common.css

70 ms

all.css

all.css

64 ms

v4-shims.css

v4-shims.css

85 ms

jquery-3.7.1.min.js

jquery-3.7.1.min.js

45 ms

d9fo84j1zi.jsonp

d9fo84j1zi.jsonp

49 ms

E-v1.js

E-v1.js

67 ms

api.js

api.js

73 ms

onpay-common.js

onpay-common.js

54 ms

slider.js

slider.js

54 ms

usmap.js

usmap.js

66 ms

hoverIntent.min.js

hoverIntent.min.js

55 ms

maxmegamenu.js

maxmegamenu.js

66 ms

public.js

public.js

75 ms

css2

css2

34 ms

spai-lib-bg-compat.1.1.min.js

spai-lib-bg-compat.1.1.min.js

465 ms

OnPay_Wordmark_Blue.svg

OnPay_Wordmark_Blue.svg

253 ms

recaptcha__en.js

recaptcha__en.js

334 ms

Arrow_Up_Right_Black.svg

Arrow_Up_Right_Black.svg

234 ms

OnPay_Main_Dashboard_Mock_2024_Perspective_Hi_Res-min.png

OnPay_Main_Dashboard_Mock_2024_Perspective_Hi_Res-min.png

314 ms

Forbes-Advisor_white.svg

Forbes-Advisor_white.svg

233 ms

PCMag-Logo_white.svg

PCMag-Logo_white.svg

235 ms

CNBC-logo_white.svg

CNBC-logo_white.svg

231 ms

CNN-logo_white.svg

CNN-logo_white.svg

233 ms

Arrow_Up_Right_White.svg

Arrow_Up_Right_White.svg

310 ms

OnPay_Run_Payroll_Mock.png

OnPay_Run_Payroll_Mock.png

314 ms

Arrow_Up_Right_Green.svg

Arrow_Up_Right_Green.svg

310 ms

Checkmark_Green.svg

Checkmark_Green.svg

312 ms

Arrow_Right_Green.svg

Arrow_Right_Green.svg

308 ms

OnPay_Wordmark_White.svg

OnPay_Wordmark_White.svg

396 ms

Grid-Background-Rectangle-Blue.svg

Grid-Background-Rectangle-Blue.svg

308 ms

Grid-Background-Rectangle-White.svg

Grid-Background-Rectangle-White.svg

310 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

240 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

282 ms

pxiByp8kv8JHgFVrLDD4V1s.ttf

pxiByp8kv8JHgFVrLDD4V1s.ttf

327 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

328 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

341 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

339 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

341 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

341 ms

pxiGyp8kv8JHgFVrLPTedw.ttf

pxiGyp8kv8JHgFVrLPTedw.ttf

341 ms

fa-brands-400.ttf

fa-brands-400.ttf

201 ms

fa-brands-400.ttf

fa-brands-400.ttf

394 ms

wARDj0u

wARDj0u

36 ms

pxiGyp8kv8JHgFVrJJLedw.ttf

pxiGyp8kv8JHgFVrJJLedw.ttf

340 ms

pxiDyp8kv8JHgFVrJJLmg1hlEA.ttf

pxiDyp8kv8JHgFVrJJLmg1hlEA.ttf

395 ms

pxiDyp8kv8JHgFVrJJLm21llEA.ttf

pxiDyp8kv8JHgFVrJJLm21llEA.ttf

394 ms

pxiDyp8kv8JHgFVrJJLmv1plEA.ttf

pxiDyp8kv8JHgFVrJJLmv1plEA.ttf

394 ms

pxiAyp8kv8JHgFVrJJLmE3tF.ttf

pxiAyp8kv8JHgFVrJJLmE3tF.ttf

395 ms

pxiDyp8kv8JHgFVrJJLmr19lEA.ttf

pxiDyp8kv8JHgFVrJJLmr19lEA.ttf

395 ms

pxiDyp8kv8JHgFVrJJLmy15lEA.ttf

pxiDyp8kv8JHgFVrJJLmy15lEA.ttf

395 ms

pxiDyp8kv8JHgFVrJJLm111lEA.ttf

pxiDyp8kv8JHgFVrJJLm111lEA.ttf

396 ms

pxiDyp8kv8JHgFVrJJLm81xlEA.ttf

pxiDyp8kv8JHgFVrJJLm81xlEA.ttf

396 ms

popover.js

popover.js

65 ms

wistia-mux.js

wistia-mux.js

87 ms

flashPlayer.js

flashPlayer.js

151 ms

Accessibility Review

onpay.com accessibility score

73

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

onpay.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

onpay.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onpay.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Onpay.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

onpay.com

Open Graph data is detected on the main page of On Pay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: