11.7 sec in total
1.6 sec
9.8 sec
215 ms
Visit onsort.fr now to see the best up-to-date Onsort content and also check out these interesting facts you probably never knew about onsort.fr
Depuis 2003, le Réseau Onsort fait vivre l'humour à Lille ! Impro, One-Man Show, théâtre... Facilitez-vous le spectacle vivant, découvrez notre programmation !
Visit onsort.frWe analyzed Onsort.fr page load time and found that the first response time was 1.6 sec and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
onsort.fr performance score
1646 ms
264 ms
344 ms
250 ms
691 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 62% of them (80 requests) were addressed to the original Onsort.fr, 12% (15 requests) were made to Static.xx.fbcdn.net and 9% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Onsort.fr.
Page size can be reduced by 1.1 MB (53%)
2.1 MB
967.1 kB
In fact, the total size of Onsort.fr main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 845.5 kB which makes up the majority of the site volume.
Potential reduce by 38.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. 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 38.4 kB or 75% of the original size.
Potential reduce by 27.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. Onsort images are well optimized though.
Potential reduce by 603.7 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 603.7 kB or 71% of the original size.
Potential reduce by 439.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. Onsort.fr needs all CSS files to be minified and compressed as it can save up to 439.5 kB or 79% of the original size.
Number of requests can be reduced by 90 (79%)
114
24
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Onsort. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
www.onsort.fr
1646 ms
wp-emoji-release.min.js
264 ms
style.css
344 ms
flick.css
250 ms
www.onsort.fr
691 ms
dashicons.min.css
326 ms
extra.min.css
174 ms
styles.css
285 ms
events_manager.css
375 ms
magnific-popup.css
356 ms
go_portfolio_styles.css
471 ms
sidebar-login.css
420 ms
style.css
525 ms
css
25 ms
css
37 ms
style.css
482 ms
style.css
480 ms
style.css
520 ms
style.css
571 ms
jetpack.css
650 ms
jquery-ui-1.8.16.custom.css
579 ms
custom.css
624 ms
jquery.js
742 ms
jquery-migrate.min.js
678 ms
scrollTo.js
690 ms
jquery.form.min.js
740 ms
mailchimp.js
764 ms
core.min.js
796 ms
datepicker.js
873 ms
widget.min.js
796 ms
position.min.js
833 ms
mouse.min.js
835 ms
sortable.min.js
845 ms
datepicker.min.js
964 ms
menu.min.js
888 ms
autocomplete.min.js
922 ms
resizable.min.js
929 ms
draggable.min.js
940 ms
devicepx-jetpack.js
4 ms
gprofiles.js
54 ms
e-201611.js
4 ms
gsom.css
928 ms
button.min.js
817 ms
dialog.min.js
773 ms
events-manager.js
773 ms
jquery.blockUI.min.js
757 ms
sidebar-login.min.js
744 ms
swfobject.js
735 ms
scripts.js
758 ms
jquery.magnific-popup.min.js
771 ms
jquery.isotope.min.js
727 ms
jquery.carouFredSel-6.2.1-packed.js
750 ms
jquery.touchSwipe.min.js
701 ms
go_portfolio_scripts.js
703 ms
wpgroho.js
662 ms
tie-scripts.js
706 ms
jquery.cycle2.min.js
777 ms
jquery.cycle2.carousel.min.js
674 ms
jquery.cycle2.swipe.min.js
640 ms
jquery.cycle2.tile.min.js
613 ms
jquery.cycle2.video.min.js
616 ms
script.js
648 ms
script.js
653 ms
client.js
621 ms
jquery.fullcalendar.min.js
722 ms
jquery.simplemodal.1.4.3.min.js
620 ms
jquery.mousewheel.min.js
628 ms
jquery.jgrowl.min.js
685 ms
jquery.ui.datepicker-fr.js
610 ms
jquery.init_show_calendar.js
649 ms
wp-embed.min.js
646 ms
jquery.cycle.all.js
648 ms
body-bg10.png
602 ms
LogoNeutre-1.png
600 ms
HI-OmarMeftah-620x330.jpg
603 ms
IT-TrompelOeil-620x330.jpg
661 ms
MI-TrompelOeil-620x330.png
804 ms
Capture-d%E2%80%99%C3%A9cran-2016-03-16-%C3%A0-19.42.07-1-e1458154050455-300x160.png
5762 ms
Blog_ImproKeith-300x160.png
894 ms
HeaderBG1.png
1273 ms
top-shadow.png
622 ms
black-loader.gif
712 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
26 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
28 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
26 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
27 ms
4cKlrioa77J2iqTqBgkRWg.ttf
25 ms
tiefontello.svg
806 ms
tiefontello.woff
879 ms
LqowQDslGv4DmUBAfWa2Vw.ttf
26 ms
2HG_tEPiQ4Z6795cGfdivKCWcynf_cDxXwCLxiixG1c.ttf
26 ms
gc5ZVKiLNkRdGlU3GaSVBfesZW2xOQ-xsNqO47m55DA.ttf
29 ms
HkF_qI1x_noxlxhrhMQYEKCWcynf_cDxXwCLxiixG1c.ttf
26 ms
VNUH7ZAcagYBWsAiBBCEY6CWcynf_cDxXwCLxiixG1c.ttf
27 ms
sidebar-bullet.png
848 ms
6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==
30 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
29 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
30 ms
sdk.js
273 ms
185 ms
xd_arbiter.php
226 ms
xd_arbiter.php
434 ms
hovercard.css
54 ms
services.css
58 ms
g.gif
16 ms
page.php
242 ms
LUdypCgtRlc.css
283 ms
Hy2B8ciSPhU.css
353 ms
q68gy-v_YMF.js
490 ms
4D4UiA9M0SK.js
619 ms
ihptErjAmMX.js
557 ms
1BQnIVjTFoC.js
637 ms
CZfzbakm8cM.js
637 ms
cUsKAwzqrQw.js
741 ms
12512456_1062385297116590_3204196801996669953_n.png
558 ms
10401910_1029428760412244_8460707788531411012_n.png
654 ms
308111_10151243576378530_1893989631_n.jpg
722 ms
1910615_120580694993284_1509779665123159641_n.jpg
788 ms
270119_143921909022249_635510_n.jpg
765 ms
11014902_10206686879193089_4484101328053683993_n.jpg
765 ms
12745878_10208515478386760_3122006325582940901_n.jpg
762 ms
10472157_10207437570291009_5986700388199189159_n.jpg
765 ms
12553081_110455639338683_8287151820670583203_n.jpg
789 ms
wL6VQj7Ab77.png
123 ms
s7jcwEQH7Sx.png
123 ms
6GqoI2ZyIrf.png
71 ms
R9a_DtVRZgv.js
71 ms
cUDgRFxaoIk.js
69 ms
0JBr1QHp8Gi.js
73 ms
kDOzhTr2W91.js
70 ms
onsort.fr SEO score
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onsort.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 Onsort.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.
onsort.fr
Open Graph data is detected on the main page of Onsort. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: