4.5 sec in total
216 ms
3.6 sec
693 ms
Visit whoz.com now to see the best up-to-date Whoz content and also check out these interesting facts you probably never knew about whoz.com
Whoz is the best-in-class cloud solution to double professional services margin and talent engagement. Powered by a skills hub, Whoz allows organizations to connect their talent ecosystem to their bus...
Visit whoz.comWe analyzed Whoz.com page load time and found that the first response time was 216 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
whoz.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value9.5 s
0/100
25%
Value8.7 s
16/100
10%
Value1,020 ms
26/100
30%
Value0.143
78/100
15%
Value13.0 s
12/100
10%
216 ms
391 ms
455 ms
94 ms
186 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 80% of them (40 requests) were addressed to the original Whoz.com, 6% (3 requests) were made to Api.plezi.co and 4% (2 requests) were made to Brain.plezi.co. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Whoz.com.
Page size can be reduced by 321.3 kB (28%)
1.1 MB
809.2 kB
In fact, the total size of Whoz.com main page is 1.1 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. 35% of websites need less resources to load. Images take 877.0 kB which makes up the majority of the site volume.
Potential reduce by 58.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 58.0 kB or 78% of the original size.
Potential reduce by 163.0 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, Whoz needs image optimization as it can save up to 163.0 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 85.6 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 85.6 kB or 78% of the original size.
Potential reduce by 14.7 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. Whoz.com needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 21% of the original size.
Number of requests can be reduced by 27 (60%)
45
18
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whoz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
whoz.com
216 ms
whoz.com
391 ms
455 ms
style.min.css
94 ms
theme.min.css
186 ms
classic-themes.min.css
272 ms
style.css
275 ms
style.css
368 ms
ossleads_analytics.js
331 ms
scripts
493 ms
gsap.min.js
440 ms
scroll-trigger.min.js
455 ms
scroll-to.min.js
365 ms
swiper.min.js
548 ms
homepage.js
440 ms
scripts.min.js
493 ms
lottie-light.min.js
549 ms
whoz-lottie.js
495 ms
whoz-tabs.js
495 ms
timeline.js
543 ms
verbatims.js
562 ms
analytics
251 ms
gtm.js
124 ms
whoz-demo.png
281 ms
HP_PICTO_CARTOGRAPHIE-1.svg
198 ms
HP_PICTO_GESTION-PORTEFEUILLE-PROJETS.svg
230 ms
HP_PICTO_ANALYSE_DE_PERFORMANCES.svg
246 ms
PICTO_CONFIANCE_NUMERIQUE.svg
244 ms
PICTO_INTEGRATION.svg
258 ms
PICTO_BLOG.svg
293 ms
PICTO_LIVRES.svg
318 ms
PICTO_EVENEMENTS.svg
338 ms
PICTO_PRESSE-ET-ACTUALITE-1.svg
336 ms
whoz-logo.png
530 ms
Clients-reviews-of-Whoz-BLUE.gif
1665 ms
Fonctionnalite.png
390 ms
Sebastien-Barrot-CS-Group-1.jpg
407 ms
Eric-Cohen-orange-carre.png
523 ms
Ahmed-Morjane_Econocom.jpeg
428 ms
Jerome-Motte-orange-carre.png
578 ms
JF-Fellman-orange-carre.png
670 ms
Pierre-Beranger-orange-carre.png
614 ms
Image.png
885 ms
Image2.png
803 ms
insight.min.js
51 ms
uc.js
88 ms
matomo.js
445 ms
analytics
360 ms
create
91 ms
create
110 ms
whoz.com 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
whoz.com 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
Page has valid source maps
whoz.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Whoz.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 Whoz.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.
whoz.com
Open Graph data is detected on the main page of Whoz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: