Tools & Wizards About Us
whoz.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

whoz.com

Cloud-based Professional Services solution ⎮ Skills and Talent Deployment

Page Load Speed

3.5 sec in total

First Response

180 ms

Resources Loaded

2.7 sec

Page Rendered

639 ms

whoz.com screenshot

About Website

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.com

Key Findings

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

Performance Metrics

whoz.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value850 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

whoz.com

180 ms

whoz.com

333 ms

374 ms

style.min.css

86 ms

theme.min.css

172 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 92% of them (67 requests) were addressed to the original Whoz.com, 3% (2 requests) were made to Api.plezi.co and 1% (1 request) were made to App.plezi.co. The less responsive or slowest element that took the longest time to load (753 ms) belongs to the original domain Whoz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 292.4 kB (15%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Whoz.com main page is 1.9 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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 71.0 kB

  • Original 87.8 kB
  • After minification 82.9 kB
  • After compression 16.8 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 71.0 kB or 81% of the original size.

Image Optimization

-12%

Potential reduce by 206.6 kB

  • Original 1.8 MB
  • After minification 1.6 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. Obviously, Whoz needs image optimization as it can save up to 206.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-21%

Potential reduce by 14.8 kB

  • Original 69.5 kB
  • After minification 69.5 kB
  • After compression 54.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.8 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (36%)

Requests Now

69

After Optimization

44

  • Images
  • JavaScript
  • CSS

The browser has sent 69 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 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whoz.com

whoz.com

180 ms

whoz.com

whoz.com

333 ms

374 ms

style.min.css

style.min.css

86 ms

theme.min.css

theme.min.css

172 ms

classic-themes.min.css

classic-themes.min.css

252 ms

style.css

style.css

256 ms

style.css

style.css

333 ms

ossleads_analytics.js

ossleads_analytics.js

331 ms

gsap.min.js

gsap.min.js

433 ms

scroll-trigger.min.js

scroll-trigger.min.js

440 ms

scroll-to.min.js

scroll-to.min.js

418 ms

swiper.min.js

swiper.min.js

515 ms

homepage.js

homepage.js

419 ms

scripts.min.js

scripts.min.js

432 ms

lottie-light.min.js

lottie-light.min.js

591 ms

whoz-lottie.js

whoz-lottie.js

460 ms

whoz-tabs.js

whoz-tabs.js

510 ms

timeline.js

timeline.js

510 ms

verbatims.js

verbatims.js

511 ms

analytics

analytics

354 ms

gtm.js

gtm.js

135 ms

whoz-demo.png

whoz-demo.png

260 ms

HP_PICTO_CARTOGRAPHIE-1.svg

HP_PICTO_CARTOGRAPHIE-1.svg

255 ms

HP_PICTO_GESTION-PORTEFEUILLE-PROJETS.svg

HP_PICTO_GESTION-PORTEFEUILLE-PROJETS.svg

256 ms

HP_PICTO_ANALYSE_DE_PERFORMANCES.svg

HP_PICTO_ANALYSE_DE_PERFORMANCES.svg

257 ms

PICTO_CONFIANCE_NUMERIQUE.svg

PICTO_CONFIANCE_NUMERIQUE.svg

258 ms

PICTO_INTEGRATION.svg

PICTO_INTEGRATION.svg

313 ms

PICTO_BLOG.svg

PICTO_BLOG.svg

309 ms

PICTO_LIVRES.svg

PICTO_LIVRES.svg

312 ms

PICTO_EVENEMENTS.svg

PICTO_EVENEMENTS.svg

316 ms

PICTO_PRESSE-ET-ACTUALITE-1.svg

PICTO_PRESSE-ET-ACTUALITE-1.svg

321 ms

whoz-logo.png

whoz-logo.png

416 ms

PICTO_BOOKING-DE-TALENTS-vio-1.png

PICTO_BOOKING-DE-TALENTS-vio-1.png

391 ms

Copy-of-PICTO_EXPLORER-IMPACTS-violet.png

Copy-of-PICTO_EXPLORER-IMPACTS-violet.png

394 ms

PICTO_ECLAIRER-vio.png

PICTO_ECLAIRER-vio.png

397 ms

PICTO_TROUVER-vio.png

PICTO_TROUVER-vio.png

400 ms

egis-1.png

egis-1.png

404 ms

Econocom-1.png

Econocom-1.png

471 ms

logo-group.png

logo-group.png

475 ms

ATOS.png

ATOS.png

480 ms

CAP.PA_BIG.D.png

CAP.PA_BIG.D.png

483 ms

orange-1-e1717751539259.png

orange-1-e1717751539259.png

489 ms

akkodiis.png

akkodiis.png

502 ms

AYMING-e1717749850207.png

AYMING-e1717749850207.png

552 ms

Design-sans-titre-12-e1717749472745.png

Design-sans-titre-12-e1717749472745.png

558 ms

devoteam-1.png

devoteam-1.png

512 ms

smart4.png

smart4.png

513 ms

OPEN.png

OPEN.png

520 ms

insight.min.js

insight.min.js

56 ms

keyrus-1.png

keyrus-1.png

514 ms

mc2i-1.png

mc2i-1.png

560 ms

thales.png

thales.png

546 ms

Portail-Partenaires.png

Portail-Partenaires.png

540 ms

insight_tag_errors.gif

insight_tag_errors.gif

142 ms

PICTO_TROUVER.png

PICTO_TROUVER.png

505 ms

PICTO_GESTION-DE-COMPTES.png

PICTO_GESTION-DE-COMPTES.png

512 ms

PICTO_AFFECTER.png

PICTO_AFFECTER.png

528 ms

PICTO_GAGNER.png

PICTO_GAGNER.png

563 ms

PICTO_EMPLOYER.png

PICTO_EMPLOYER.png

469 ms

PICTO_SUIVER.png

PICTO_SUIVER.png

478 ms

PICTO_MATCHER.png

PICTO_MATCHER.png

478 ms

PICTO_FLUIDIFIER.png

PICTO_FLUIDIFIER.png

485 ms

PICTO_DECIDER.png

PICTO_DECIDER.png

502 ms

PICTO_SAISSISER.png

PICTO_SAISSISER.png

538 ms

PICTO_EXPLORER.png

PICTO_EXPLORER.png

495 ms

Visuel-2.jpg

Visuel-2.jpg

753 ms

Capture-decran-2024-02-21-a-11.17.06.png

Capture-decran-2024-02-21-a-11.17.06.png

752 ms

Capture-decran-2024-02-19-a-19.04.56.png

Capture-decran-2024-02-19-a-19.04.56.png

673 ms

create

create

91 ms

Capture-decran-2024-02-19-a-19.04.46.png

Capture-decran-2024-02-19-a-19.04.46.png

527 ms

Image.png

Image.png

566 ms

Image2.png

Image2.png

652 ms

Accessibility Review

whoz.com accessibility score

82

Accessibility Issues

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

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

High

Image elements do not have [alt] attributes

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

whoz.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

whoz.com SEO score

93

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

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

High

Document uses legible font sizes

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 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.

Social Sharing Optimization

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: