2.9 sec in total
370 ms
2.2 sec
266 ms
Click here to check amazing Whos Off content. Otherwise, check out these important facts you probably never knew about whosoff.co.uk
WhosOff is the leading professional employee holiday tracker that allows you to manage your staff leave. Sign up today for your FREE trial.
Visit whosoff.co.ukWe analyzed Whosoff.co.uk page load time and found that the first response time was 370 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
whosoff.co.uk performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value4.4 s
40/100
25%
Value2.9 s
94/100
10%
Value1,410 ms
16/100
30%
Value0
100/100
15%
Value10.0 s
26/100
10%
370 ms
158 ms
166 ms
169 ms
168 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whosoff.co.uk, 3% (2 requests) were made to Googleadservices.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Whosoff.com.
Page size can be reduced by 1.0 MB (46%)
2.2 MB
1.2 MB
In fact, the total size of Whosoff.co.uk main page is 2.2 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. 20% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 23.4 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. This page needs HTML code to be minified as it can gain 5.0 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.4 kB or 78% of the original size.
Potential reduce by 960.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. Obviously, Whos Off needs image optimization as it can save up to 960.6 kB or 46% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 11.9 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 11.9 kB or 33% of the original size.
Potential reduce by 18.5 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. Whosoff.co.uk needs all CSS files to be minified and compressed as it can save up to 18.5 kB or 80% of the original size.
Number of requests can be reduced by 34 (64%)
53
19
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whos Off. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.whosoff.com
370 ms
normalize.min.css
158 ms
base.css
166 ms
content.css
169 ms
base.css
168 ms
css
24 ms
logo.png
542 ms
tv.png
874 ms
awards.png
686 ms
public-mobiles-appstore.jpg
325 ms
public-mobiles-appworld.jpg
363 ms
public-mobiles-androidmarketplace.jpg
337 ms
mobile-apps.png
935 ms
home-no-hidden-costs.png
501 ms
jquery-1.11.2.min.js
9 ms
conversion_async.js
18 ms
base.js
375 ms
google-remarketing.js
469 ms
slider.js
515 ms
home-anim.js
552 ms
scrollingWorldFlags.js
567 ms
scrollingClientLogos.js
597 ms
bg.png
1108 ms
nav-bg.png
543 ms
mast-logo.png
569 ms
Freescpt-webfont.woff
505 ms
google.js
369 ms
analytics.js
42 ms
55 ms
caseStudies.ashx
567 ms
uk.gif
90 ms
de.gif
96 ms
US.gif
91 ms
AU.gif
101 ms
CA.gif
169 ms
SI.gif
169 ms
IE.gif
171 ms
BR.gif
192 ms
ES.gif
196 ms
AE.gif
252 ms
FR.gif
251 ms
DK.gif
253 ms
NL.gif
285 ms
NZ.gif
287 ms
SG.gif
331 ms
NO.gif
332 ms
MX.gif
334 ms
CH.gif
382 ms
CN.gif
384 ms
collect
18 ms
42 ms
collect
65 ms
40 ms
iirsm-logo.jpg
83 ms
adlens-case-study.png
85 ms
ravensworth-logo.png
181 ms
imperial-college-healthcare-charity-logo.jpg
86 ms
print.css
83 ms
whosoff.co.uk 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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
whosoff.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
whosoff.co.uk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whosoff.co.uk 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 Whosoff.co.uk 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.
whosoff.co.uk
Open Graph data is detected on the main page of Whos Off. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: