1.5 sec in total
277 ms
1.1 sec
189 ms
Click here to check amazing Projet Homere content for Greece. Otherwise, check out these important facts you probably never knew about projethomere.com
Portail Grec moderne, classique proposant cours gratuits, videotheque, bibliotheque, auteurs, dialectes, ressources
Visit projethomere.comWe analyzed Projethomere.com page load time and found that the first response time was 277 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
projethomere.com performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value1.9 s
98/100
25%
Value3.7 s
85/100
10%
Value580 ms
51/100
30%
Value0.098
90/100
15%
Value10.6 s
23/100
10%
277 ms
91 ms
21 ms
67 ms
41 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 37% of them (23 requests) were addressed to the original Projethomere.com, 34% (21 requests) were made to Static.xx.fbcdn.net and 6% (4 requests) were made to Widget.calameo.com. The less responsive or slowest element that took the longest time to load (511 ms) relates to the external source Widget.calameo.com.
Page size can be reduced by 160.1 kB (28%)
574.9 kB
414.8 kB
In fact, the total size of Projethomere.com main page is 574.9 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. 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. CSS take 426.2 kB which makes up the majority of the site volume.
Potential reduce by 38.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 38.8 kB or 80% of the original size.
Potential reduce by 6.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. Projet Homere images are well optimized though.
Potential reduce by 62 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 114.4 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. Projethomere.com needs all CSS files to be minified and compressed as it can save up to 114.4 kB or 27% of the original size.
Number of requests can be reduced by 36 (65%)
55
19
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Projet Homere. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
projethomere.com
277 ms
main.css
91 ms
addthis_widget.js
21 ms
show_ads.js
67 ms
t_small-a.png
41 ms
lg-share-fr.gif
103 ms
geocounter.php
349 ms
1 ms
Projethomere.gif
201 ms
publications-homere.jpg
200 ms
image-site.jpg
200 ms
main_right.gif
199 ms
grec.JPG
200 ms
anglais.jpg
200 ms
allemand.JPG
341 ms
espagnol.JPG
339 ms
portugal.JPG
340 ms
italien.JPG
341 ms
romania.JPG
341 ms
russe.JPG
341 ms
arabe.JPG
343 ms
israel.JPG
343 ms
china.JPG
343 ms
japonais.JPG
360 ms
feed-icon-28x28.png
359 ms
recherche.png
361 ms
mail.png
428 ms
facebook.jpg
426 ms
puce.gif
427 ms
analytics.js
21 ms
102 ms
likebox.php
181 ms
collect
13 ms
js
58 ms
css
76 ms
main.css
511 ms
library.js
12 ms
09v35hHCG22.css
20 ms
bqx3InLoTuC.css
22 ms
tvUlv14hXs-.css
25 ms
7iK8-lsXHFs.js
28 ms
vxmlpLbAeCj.js
24 ms
o1ndYS2og_B.js
23 ms
_02W6YRik00.js
57 ms
qJoe20iyDr0.js
25 ms
p55HfXW__mM.js
27 ms
k_PjgALRjoR.js
55 ms
CwUW1mXVRXb.js
60 ms
CGo9cU7zbWd.js
73 ms
EcPi7SsydEO.js
59 ms
cjzsuKU-ivU.js
80 ms
kgAz0TBWoYE.js
72 ms
kww4kc8mdjt.js
71 ms
HzxD9aAXSyD.js
87 ms
Q-X-GXL_I_5.js
90 ms
303505021_586034456513740_1382381778443648572_n.jpg
38 ms
OcmMPieTVMv.js
10 ms
cL2K70J5_dl.js
11 ms
305996805_586034453180407_1681917862203956561_n.jpg
50 ms
UXtr_j2Fwe-.png
7 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
21 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
20 ms
projethomere.com 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
projethomere.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
projethomere.com SEO score
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
N/A
FR
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Projethomere.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is French. Our system also found out that Projethomere.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
projethomere.com
Open Graph description is not detected on the main page of Projet Homere. 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: