5.2 sec in total
279 ms
4.5 sec
418 ms
Visit leve.ht now to see the best up-to-date LEVE content and also check out these interesting facts you probably never knew about leve.ht
L'Association LEVE milite pour le respect des droits linguistiques des citoyens haïtiens. Elle démocratise le savoir par la traduction en créole haïtien d’œuvres majeures de la littérature mondia...
Visit leve.htWe analyzed Leve.ht page load time and found that the first response time was 279 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
leve.ht performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value6.9 s
6/100
25%
Value10.1 s
9/100
10%
Value2,130 ms
7/100
30%
Value0.052
99/100
15%
Value21.4 s
1/100
10%
279 ms
1695 ms
578 ms
560 ms
738 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Leve.ht, 87% (94 requests) were made to Files.gandi.ws and 9% (10 requests) were made to 55b558c7-resources.gandi.ws. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Editions.leve.ht.
Page size can be reduced by 5.4 MB (36%)
15.1 MB
9.7 MB
In fact, the total size of Leve.ht main page is 15.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. 70% of websites need less resources to load. Images take 12.2 MB which makes up the majority of the site volume.
Potential reduce by 1.0 MB
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 1.0 MB or 90% of the original size.
Potential reduce by 4.4 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, LEVE needs image optimization as it can save up to 4.4 MB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 90 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 0 B
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. Leve.ht has all CSS files already compressed.
Number of requests can be reduced by 6 (8%)
72
66
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LEVE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
leve.ht
279 ms
editions.leve.ht
1695 ms
2298ccc8-8bf7-404c-a183-aa230f8c7565.css
578 ms
translations.js
560 ms
published-v10-site-libs.js
738 ms
published-v8-site.js
1105 ms
twig-widget-views-v2.js
559 ms
scroll-out.js
547 ms
jquery.min.js
558 ms
ga.js
106 ms
logo2leve_1.png
319 ms
a2d4881d-b4ab-4865-bba4-9883c903cc06.JPG
322 ms
45e97f5c-b51e-4a6e-8dac-3d828ee06ed4.png
718 ms
a93f1115-b077-493f-a69d-1bc237a9c1f2.png
728 ms
20d52b4b-a41b-46bd-a99e-eb8be31e4147.png
759 ms
aqlose.jpg
433 ms
thestranger-yonngapa.png
405 ms
da1.png
671 ms
e15355f9-36ed-461e-be42-735b61dbb54e.PNG
576 ms
yna1_1.png
609 ms
96319489-670a-4650-85bb-4465710b740f.png
739 ms
lbdmeuf.png
871 ms
dezafi.png
728 ms
leupsiv.jpg
807 ms
zb2.png
894 ms
alrlv.png
1285 ms
r.png
828 ms
mld.png
930 ms
rcdlth.jpg
898 ms
ale_1.png
993 ms
lle.png
960 ms
gdlr.png
1059 ms
bg_1.png
1070 ms
hsii.png
1018 ms
yna2.png
1050 ms
p.png
1078 ms
3fdh.png
1194 ms
zaw.png
1225 ms
ldvln.png
1144 ms
ts.png
1152 ms
abdlpch.jpg
1158 ms
le.png
1228 ms
lpd_2.png
1239 ms
e.png
1251 ms
vc2_1.png
1375 ms
basket-dark.svg
173 ms
ampersand-bg.jpg
425 ms
etpplm.png
1244 ms
FontAwesome.woff
92 ms
fontawesome-webfont.woff
165 ms
__utm.gif
20 ms
jn.png
996 ms
vnvrvf.png
1003 ms
mdlaph2.jpg
933 ms
jsa.jpg
935 ms
a25017.jpg
913 ms
camus_petit.png
799 ms
aplo.png
738 ms
mchauvet.jpg
710 ms
ll.png
1357 ms
images.jpg
740 ms
s.png
764 ms
jacques_roumain.jpg
738 ms
mb.png
703 ms
franketienne.png
731 ms
lrdp.jpg
618 ms
saintex1.jpg
595 ms
rag.png
590 ms
cafe-litteraire-belgo-haitien-en-hommage-a-jacques-stephen-alexis.jpg
559 ms
dfplh.png
529 ms
dl_5.png
496 ms
lr.jpg
471 ms
dsjpp.png
440 ms
kettlymars_petit.png
431 ms
dlo_b.png
420 ms
b858a6d0-de4a-4f53-84b9-ac25cae77e38.jpg
411 ms
lme.png
346 ms
e5ad6ff9-87cd-4657-b99c-bdc7f0b8303b.jpg
338 ms
cd.png
331 ms
mdlph.jpg
297 ms
lme_1.png
266 ms
2f871126-2df1-436e-83eb-e620dbff5e71.jpg
261 ms
0140bba6-4b17-4b94-bbf6-6c77bf1f3139.jpg
251 ms
lpncqdg.png
239 ms
lqdcs.png
207 ms
hdtmr_1.png
177 ms
ldnee.png
175 ms
ab.png
169 ms
lbah.png
156 ms
pa.png
125 ms
cdlhcif.png
116 ms
cec.png
85 ms
tnv.png
83 ms
sp.png
65 ms
mecm.png
24 ms
2f6a9181-49aa-4f9b-b140-4809cff8ed51.PNG
112 ms
7f87a5a7-8cfb-4b73-ba59-2ec272680e84.PNG
131 ms
9bc6559e-a7d1-49c8-a579-f1a4f6f34110.jpg
103 ms
5fd62a79-4460-41f6-81d8-750b16209401.JPG
159 ms
d99b49b1-3da8-4311-8989-661997471ef2.JPG
186 ms
a4c610eb-72c1-4afd-95f1-4573d973dae1.JPG
195 ms
4be89c05-75b8-4e1f-8306-f773db479d36.JPG
227 ms
80eea53a-2c87-481b-ba9e-56f3b056b478.jpg
548 ms
b19c6800-cf2f-4303-bbd4-51e849c603a9.jpeg
254 ms
7afa109f-d76e-4e36-8948-ddd4f522ffde.jpeg
272 ms
7de4b28f-e908-4b15-acab-4f54cb199361.JPG
290 ms
687c1acb-d12e-4d9b-81b3-47f3c6a2f842.png
402 ms
0f97a53d-8769-47dd-9447-d22198ed46bb.JPG
343 ms
leve.ht 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
leve.ht 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
Missing source maps for large first-party JavaScript
leve.ht SEO score
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
Tap targets are not sized appropriately
![]()
HT
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leve.ht can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed English language. Our system also found out that Leve.ht 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.
leve.ht
Open Graph data is detected on the main page of LEVE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: