5.7 sec in total
1.2 sec
4.2 sec
199 ms
Welcome to olympictruce.org homepage info - get ready to check Olympic Truce best content right away, or after learning these important things about olympictruce.org
Visit olympictruce.orgWe analyzed Olympictruce.org page load time and found that the first response time was 1.2 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
olympictruce.org performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value4.3 s
42/100
25%
Value9.6 s
11/100
10%
Value1,140 ms
22/100
30%
Value0.024
100/100
15%
Value10.5 s
24/100
10%
1234 ms
586 ms
481 ms
351 ms
370 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 85% of them (64 requests) were addressed to the original Olympictruce.org, 7% (5 requests) were made to Apis.google.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Olympictruce.org.
Page size can be reduced by 927.7 kB (48%)
1.9 MB
1.0 MB
In fact, the total size of Olympictruce.org main page is 1.9 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. 40% of websites need less resources to load. Javascripts take 805.3 kB which makes up the majority of the site volume.
Potential reduce by 48.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 48.9 kB or 81% of the original size.
Potential reduce by 57.4 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. Olympic Truce images are well optimized though.
Potential reduce by 557.6 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 557.6 kB or 69% of the original size.
Potential reduce by 263.8 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. Olympictruce.org needs all CSS files to be minified and compressed as it can save up to 263.8 kB or 83% of the original size.
Number of requests can be reduced by 51 (71%)
72
21
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olympic Truce. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
index.php
1234 ms
e27b26f27a0f5007d214cef04981a511.js
586 ms
k2.css
481 ms
widgetkit-62942019.css
351 ms
rokbox.css
370 ms
grid-12.css
248 ms
gantry-core.css
372 ms
joomla-core.css
506 ms
main-light.css
478 ms
utilities.css
500 ms
typography.css
496 ms
font-awesome.css
617 ms
thirdparty-k2.css
618 ms
thirdparty-k2-light.css
625 ms
demo-styles.css
620 ms
template.css
631 ms
template-gecko.css
699 ms
style.css
711 ms
front.css
720 ms
mod_tz_new_marquee.css
737 ms
mod_tz_news.css
746 ms
slider.css
748 ms
style.css
815 ms
228450e631fe6cda62ce24fed184d0cf.css
827 ms
mootools-core.js
1084 ms
core.js
860 ms
jquery.min.js
43 ms
k2.js
879 ms
caption.js
863 ms
jquery.js
1054 ms
widgetkit-ffb193bc.js
943 ms
mootools-more.js
1466 ms
rokbox.js
1129 ms
gantry-totop.js
1000 ms
browser-engines.js
1063 ms
load-transition.js
1129 ms
client.js
55 ms
engine.mootools.js
1170 ms
script.js
948 ms
mod_tz_news.slides.js
959 ms
jquery.simplyscroll.min.js
881 ms
ytc.jquery-1.5.min.js
1010 ms
script.js
924 ms
lightbox.js
177 ms
mediaelement-and-player.js
200 ms
spotlight.js
243 ms
cb=gapi.loaded_0
43 ms
analytics.js
28 ms
facebook.png
136 ms
twitter.png
134 ms
feed.png
134 ms
youtube.png
134 ms
el.gif
132 ms
en.gif
132 ms
LOGO_TRANS.png
254 ms
9979ce693a9a255e6b737fe15474be54.png
249 ms
0e09527b0f5edaa60cf5702119e6a0a2_XL.jpg
714 ms
ebe9ac202a3149b75a8ae8adb2e1d8a7_XL.jpg
371 ms
a9ccd7cd1c4267a50c67ac0bd7180172_XL.jpg
487 ms
forum.png
263 ms
542390225756f78888142d54f3d17e01_Generic.jpg
600 ms
c1572c59821062c96d0fc33ad32a2983_Generic.jpg
491 ms
620466077c427f141effa294382f5fba_Generic.jpg
515 ms
postmessageRelay
96 ms
collect
69 ms
Oxygen-webfont.woff
437 ms
totop.png
486 ms
loading.gif
482 ms
rotator-black.png
492 ms
pause-black.png
509 ms
3193398744-postmessagerelay.js
27 ms
rpc:shindig_random.js
63 ms
cb=gapi.loaded_0
3 ms
proxy.html
61 ms
cb=gapi.loaded_0
2 ms
olympictruce.org 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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
olympictruce.org 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
Page has valid source maps
olympictruce.org 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
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
EL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Olympictruce.org can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it does not match the claimed English language. Our system also found out that Olympictruce.org 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.
olympictruce.org
Open Graph description is not detected on the main page of Olympic Truce. 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: