7.5 sec in total
712 ms
6.3 sec
471 ms
Visit 141.gr now to see the best up-to-date 141 content and also check out these interesting facts you probably never knew about 141.gr
Visit 141.grWe analyzed 141.gr page load time and found that the first response time was 712 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
141.gr performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value1.6 s
99/100
25%
Value1.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.6 s
100/100
10%
712 ms
323 ms
32 ms
309 ms
270 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 141.gr, 70% (40 requests) were made to Data-school.gr and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Data-school.gr.
Page size can be reduced by 799.0 kB (61%)
1.3 MB
519.4 kB
In fact, the total size of 141.gr main page is 1.3 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. 45% of websites need less resources to load. CSS take 536.8 kB which makes up the majority of the site volume.
Potential reduce by 28.6 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 28.6 kB or 77% of the original size.
Potential reduce by 7.3 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. 141 images are well optimized though.
Potential reduce by 308.2 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 308.2 kB or 64% of the original size.
Potential reduce by 454.9 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. 141.gr needs all CSS files to be minified and compressed as it can save up to 454.9 kB or 85% of the original size.
Number of requests can be reduced by 27 (53%)
51
24
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 141. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
141.gr
712 ms
data-school.gr
323 ms
css
32 ms
style.css
309 ms
karma-cool-blue.css
270 ms
secondary-sky-blue.css
280 ms
_font-awesome.css
285 ms
_mobile.css
290 ms
jquery.js
447 ms
jquery-migrate.min.js
405 ms
css
63 ms
custom-main.js
419 ms
superfish.js
425 ms
jquery.flexslider.js
435 ms
jquery.fitvids.js
559 ms
jquery.isotope.js
561 ms
core.min.js
581 ms
widget.min.js
595 ms
tabs.min.js
598 ms
accordion.min.js
600 ms
jquery.prettyPhoto.js
638 ms
comment-reply.js
696 ms
wp-embed.min.js
698 ms
wp-emoji-release.min.js
724 ms
logo-am-2.jpg
158 ms
Vv5d-SCkzl0
154 ms
overlay-rays.png
268 ms
global-sprite.png
652 ms
bg-slider-jquery-2.png
268 ms
bfhep4l.png
377 ms
timthumb.php
651 ms
timthumb.php
1567 ms
timthumb.php
872 ms
bg-div-main.png
431 ms
loader-default.gif
632 ms
dimotiko-190x111.jpg
650 ms
gymnasio-190x111.jpg
651 ms
lykeio-190x111.jpg
652 ms
TELECONFERENCE-190x111.jpg
681 ms
ODIGOS_EKSETASEWN-65x65.jpg
730 ms
TRAPEZA_THEMATWN-65x65.jpg
729 ms
bg-div-footer-top.png
761 ms
bg-footer-bottom-cool-blue.png
827 ms
analytics.js
44 ms
ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
39 ms
fontawesome-webfont.woff
1101 ms
sDRi4fY9bOiJUbgq53yZCfesZW2xOQ-xsNqO47m55DA.woff
39 ms
collect
15 ms
www-embed-player-webp-vfl6OgUR7.css
117 ms
Vv5d-SCkzl0
118 ms
www-embed-player-webp-vfl6OgUR7.css
33 ms
www-embed-player.js
59 ms
base.js
92 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
58 ms
ad_status.js
57 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
90 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
97 ms
141.gr accessibility score
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
141.gr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
141.gr SEO score
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 141.gr 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 English. Our system also found out that 141.gr 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.
141.gr
Open Graph description is not detected on the main page of 141. 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: