1.5 sec in total
102 ms
657 ms
729 ms
Visit work4.io now to see the best up-to-date Work4 content and also check out these interesting facts you probably never knew about work4.io
Welcome to our home page. Work4 is the global leader in Social and Mobile Recruiting. Our technology transforms social networks into a source of top quality talent.
Visit work4.ioWe analyzed Work4.io page load time and found that the first response time was 102 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
work4.io performance score
name
value
score
weighting
Value2.7 s
58/100
10%
Value10.4 s
0/100
25%
Value7.7 s
24/100
10%
Value2,440 ms
5/100
30%
Value0.067
97/100
15%
Value17.8 s
4/100
10%
102 ms
38 ms
50 ms
69 ms
20 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Work4.io, 14% (7 requests) were made to Seiza.co. The less responsive or slowest element that took the longest time to load (162 ms) relates to the external source Pelostudio-storyblok-assets.b-cdn.net.
Page size can be reduced by 711.6 kB (9%)
7.6 MB
6.9 MB
In fact, the total size of Work4.io main page is 7.6 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 7.4 MB which makes up the majority of the site volume.
Potential reduce by 192.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 192.0 kB or 85% of the original size.
Potential reduce by 519.6 kB
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. Work4 images are well optimized though.
Number of requests can be reduced by 3 (6%)
48
45
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Work4. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
102 ms
fontawesome.min.css
38 ms
regular.min.css
50 ms
preloader.js
69 ms
webpack-runtime-a63518ca1637a3b3e79a.js
20 ms
framework-3479a0c1ade9a1ac674a.js
22 ms
app-e8be651fa395bcb77b7a.js
28 ms
filters:quality(70)
72 ms
filters:quality(70)
77 ms
filters:quality(70)
118 ms
filters:quality(70)
108 ms
filters:quality(70)
73 ms
filters:quality(70)
103 ms
filters:quality(70)
104 ms
filters:quality(70)
106 ms
filters:quality(70)
130 ms
filters:quality(70)
111 ms
filters:quality(70)
109 ms
filters:quality(70)
113 ms
filters:quality(70)
113 ms
filters:quality(70)
134 ms
filters:quality(70)
154 ms
filters:quality(70)
144 ms
filters:quality(70)
115 ms
filters:quality(70)
120 ms
filters:quality(70)
123 ms
filters:quality(70)
124 ms
filters:quality(70)
125 ms
filters:quality(70)
130 ms
filters:quality(70)
129 ms
filters:quality(70)
130 ms
filters:quality(70)
136 ms
filters:quality(70)
134 ms
filters:quality(70)
133 ms
filters:quality(70)
136 ms
filters:quality(70)
146 ms
filters:quality(70)
141 ms
filters:quality(70)
143 ms
filters:quality(70)
151 ms
filters:quality(70)
154 ms
filters:quality(70)
153 ms
filters:quality(70)
162 ms
filters:quality(70)
158 ms
filters:quality(70)
96 ms
filters:quality(70)
89 ms
filters:quality(70)
76 ms
filters:quality(70)
62 ms
filters:quality(70):format(webp)
64 ms
filters:quality(70)
65 ms
work4.io accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
work4.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
work4.io SEO score
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
Document uses legible font sizes
EN
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Work4.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Work4.io 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.
work4.io
Open Graph data is detected on the main page of Work4. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: