2.8 sec in total
330 ms
2.2 sec
207 ms
Click here to check amazing Say Who content for France. Otherwise, check out these important facts you probably never knew about saywho.fr
Comprendre qui est qui et qui fait quoi, grâce à la couverture des événements les plus confidentiels aux festivités les plus officielles.
Visit saywho.frWe analyzed Saywho.fr page load time and found that the first response time was 330 ms and then it took 2.5 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.
saywho.fr performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value14.4 s
0/100
25%
Value14.5 s
1/100
10%
Value1,560 ms
13/100
30%
Value0.554
13/100
15%
Value20.3 s
2/100
10%
330 ms
606 ms
54 ms
161 ms
253 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 68% of them (44 requests) were addressed to the original Saywho.fr, 22% (14 requests) were made to Media.saywho.fr and 8% (5 requests) were made to Fast.fonts.com. The less responsive or slowest element that took the longest time to load (767 ms) relates to the external source Media.saywho.fr.
Page size can be reduced by 79.6 kB (11%)
720.6 kB
641.0 kB
In fact, the total size of Saywho.fr main page is 720.6 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. 40% of websites need less resources to load. Images take 649.0 kB which makes up the majority of the site volume.
Potential reduce by 34.1 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 7.8 kB, which is 19% 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 34.1 kB or 82% of the original size.
Potential reduce by 33.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. Say Who images are well optimized though.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 11.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. Saywho.fr needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 90% of the original size.
Number of requests can be reduced by 34 (58%)
59
25
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Say Who. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
saywho.fr
330 ms
www.saywho.fr
606 ms
c1cc9857-8bfb-447f-ad56-2bc0afd9022e.css
54 ms
normalize.css
161 ms
style.css
253 ms
modernizr-2.8.3.min.js
257 ms
outdatedbrowser.min.css
174 ms
input-custom.css
178 ms
style.css
183 ms
colorbox.saywho.css
242 ms
validationEngine.jquery.css
287 ms
galleria.css
288 ms
jquery.isotope-custom.css
289 ms
jquery-1.11.3.min.js
429 ms
jquery-migrate-1.2.1.min.js
264 ms
jquery.imagesloaded.min.js
270 ms
jquery.colorbox-min.js
274 ms
jquery.validationEngine-fr.js
290 ms
jquery.validationEngine.js
385 ms
plugins.js
349 ms
scripts.js
351 ms
outdatedbrowser.min.js
367 ms
utils.js
369 ms
packed.js
456 ms
galleria-1.2.8-custom.js
601 ms
galleria.js
457 ms
jquery.isotope.min.js
457 ms
jquery.isotope.addon.columnshift.js
486 ms
jquery.color.js
505 ms
257320_vignette_soiree-260.jpg
509 ms
instagram-saywho.jpg
514 ms
bookez-saywho-home.png
325 ms
257166_vignette_soiree-240.jpg
511 ms
2181_vignette_intime-386.jpg
599 ms
257080_vignette_soiree-61.jpg
570 ms
256983_vignette_soiree-997.jpg
627 ms
2156_vignette_intime-73.jpg
536 ms
256849_vignette_soiree-573.jpg
687 ms
256876_vignette_soiree-396.jpg
680 ms
256772_vignette_soiree-582.jpg
720 ms
256666_vignette_soiree-240.jpg
742 ms
vignette_diaporama-627.jpg
767 ms
saywho.png
329 ms
icon_dossier.png
362 ms
disc.png
377 ms
social-icons-mini.png
408 ms
icon_document.png
417 ms
fleche_bas.png
479 ms
icon_facebook_marron.png
462 ms
icon_tweet_marron.png
470 ms
slogan.png
485 ms
c5a7f89e-15b6-49a9-8259-5ea665e72191.woff
28 ms
3fbbd6b1-cfa7-4ff0-97ea-af1b2c489f15.woff
104 ms
e2ade8a9-bd48-45e7-95e6-9dc917ba4f74.woff
79 ms
c5635d60-91fa-4e4b-8a51-41c97fc744c3.woff
83 ms
overlay.png
272 ms
ga.js
30 ms
classic-loader.gif
142 ms
classic-map.png
149 ms
__utm.gif
12 ms
image-nowm-991.jpg
347 ms
image-261.jpg
642 ms
image-nowm-513.jpg
475 ms
rond_actif.png
101 ms
rond_inactif.png
89 ms
saywho.fr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
saywho.fr 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
Issues were logged in the Issues panel in Chrome Devtools
saywho.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saywho.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 Saywho.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.
saywho.fr
Open Graph description is not detected on the main page of Say Who. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: