Tools & Wizards About Us
void.fr screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

void.fr

Agence digitale indépendante, leader de l’expérience utilisateur au Maroc. | VOID

Page Load Speed

2.5 sec in total

First Response

227 ms

Resources Loaded

1.8 sec

Page Rendered

475 ms

void.fr screenshot

About Website

Welcome to void.fr homepage info - get ready to check VOID best content for Morocco right away, or after learning these important things about void.fr

Agence digitale indépendante, leader de l’expérience utilisateur au Maroc

Visit void.fr

Key Findings

We analyzed Void.fr page load time and found that the first response time was 227 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

void.fr performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

void.fr

227 ms

void.fr

381 ms

fr

270 ms

5bf21867a7e2fa2c.css

139 ms

9c2b282206cc8551.css

208 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 77% of them (37 requests) were addressed to the original Void.fr, 13% (6 requests) were made to Fonts.gstatic.com and 8% (4 requests) were made to Backend.void.fr. The less responsive or slowest element that took the longest time to load (891 ms) relates to the external source Backend.void.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.6 kB (18%)

Content Size

476.3 kB

After Optimization

392.7 kB

  • HTML
  • Images

In fact, the total size of Void.fr main page is 476.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 383.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 79.6 kB

  • Original 92.5 kB
  • After minification 92.3 kB
  • After compression 12.9 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 79.6 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 4.0 kB

  • Original 383.8 kB
  • After minification 379.8 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. VOID images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 17 (57%)

Requests Now

30

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

void.fr

void.fr

227 ms

void.fr

void.fr

381 ms

fr

fr

270 ms

5bf21867a7e2fa2c.css

5bf21867a7e2fa2c.css

139 ms

9c2b282206cc8551.css

9c2b282206cc8551.css

208 ms

82c408b72d3b0517.css

82c408b72d3b0517.css

279 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

413 ms

933.d9ad5dbc1d25448f.js

933.d9ad5dbc1d25448f.js

265 ms

120.ce00bf45e687b8fa.js

120.ce00bf45e687b8fa.js

213 ms

webpack-129342560f962b9e.js

webpack-129342560f962b9e.js

214 ms

framework-41d8b58727bb8f36.js

framework-41d8b58727bb8f36.js

440 ms

main-e30ffa068b77759f.js

main-e30ffa068b77759f.js

448 ms

_app-4df7682831859094.js

_app-4df7682831859094.js

560 ms

020d8314-4eb9ffc5c07ea4f6.js

020d8314-4eb9ffc5c07ea4f6.js

613 ms

2edb282b-b63b89b6504edc29.js

2edb282b-b63b89b6504edc29.js

449 ms

403-29ee839fb67dc069.js

403-29ee839fb67dc069.js

516 ms

213-6907426fd5733668.js

213-6907426fd5733668.js

546 ms

273-4c7432117a43310b.js

273-4c7432117a43310b.js

482 ms

index-dc1704ea0a3b1b0a.js

index-dc1704ea0a3b1b0a.js

470 ms

_buildManifest.js

_buildManifest.js

547 ms

_ssgManifest.js

_ssgManifest.js

552 ms

css2

css2

128 ms

banque-assurance.webp

banque-assurance.webp

810 ms

image

image

639 ms

image

image

726 ms

image

image

675 ms

image

image

684 ms

image

image

697 ms

image

image

677 ms

image

image

709 ms

sante-bienetre.webp

sante-bienetre.webp

740 ms

image-cas-wafasalaf-_1_.webp

image-cas-wafasalaf-_1_.webp

891 ms

driss-fedoul_1.png

driss-fedoul_1.png

594 ms

6c72b0cb-89a1-4da9-8574-9244967bd9d6.woff

6c72b0cb-89a1-4da9-8574-9244967bd9d6.woff

344 ms

KFOlCnqEu92Fr1MmSU5vAA.woff

KFOlCnqEu92Fr1MmSU5vAA.woff

35 ms

KFOkCnqEu92Fr1MmgWxM.woff

KFOkCnqEu92Fr1MmgWxM.woff

55 ms

KFOmCnqEu92Fr1Me5g.woff

KFOmCnqEu92Fr1Me5g.woff

66 ms

KFOlCnqEu92Fr1MmEU9vAA.woff

KFOlCnqEu92Fr1MmEU9vAA.woff

67 ms

KFOlCnqEu92Fr1MmWUlvAA.woff

KFOlCnqEu92Fr1MmWUlvAA.woff

68 ms

KFOlCnqEu92Fr1MmYUtvAA.woff

KFOlCnqEu92Fr1MmYUtvAA.woff

67 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

404 ms

FuturaPT-Demi.woff

FuturaPT-Demi.woff

362 ms

FuturaPT-Book.woff

FuturaPT-Book.woff

423 ms

FuturaPT-Medium.woff

FuturaPT-Medium.woff

424 ms

FuturaPT-Light.woff

FuturaPT-Light.woff

404 ms

FuturaPT-Heavy.woff

FuturaPT-Heavy.woff

453 ms

FuturaPT-Bold.woff

FuturaPT-Bold.woff

464 ms

FuturaPT-ExtraBold.woff

FuturaPT-ExtraBold.woff

509 ms

Accessibility Review

void.fr accessibility score

85

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

void.fr SEO score

100

Search Engine Optimization Advices

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Void.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Void.fr 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

void.fr

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