4.4 sec in total
1.5 sec
2.6 sec
358 ms
Visit was.gr now to see the best up-to-date Was content for Greece and also check out these interesting facts you probably never knew about was.gr
This website is for sale! was.gr is your first and best source for information about was. Here you will also find topics relating to issues of general interest. We hope you find what you are looking f...
Visit was.grWe analyzed Was.gr page load time and found that the first response time was 1.5 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
was.gr performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value2.2 s
95/100
25%
Value1.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.5 s
100/100
10%
1465 ms
634 ms
592 ms
602 ms
557 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 35% of them (12 requests) were addressed to the original Was.gr, 12% (4 requests) were made to Makeleio.gr and 9% (3 requests) were made to Fanpage.gr. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Was.gr.
Page size can be reduced by 315.2 kB (21%)
1.5 MB
1.2 MB
In fact, the total size of Was.gr main page is 1.5 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. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 29.7 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. This page needs HTML code to be minified as it can gain 7.2 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 29.7 kB or 76% of the original size.
Potential reduce by 74.7 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. Was images are well optimized though.
Potential reduce by 68.9 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 68.9 kB or 63% of the original size.
Potential reduce by 141.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. Was.gr needs all CSS files to be minified and compressed as it can save up to 141.9 kB or 83% of the original size.
Number of requests can be reduced by 11 (44%)
25
14
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Was. 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 from 6 to 1 for CSS and as a result speed up the page load time.
was.gr
1465 ms
bootstrap.min.css
634 ms
bootstrap-theme.min.css
592 ms
font-awesome.min.css
602 ms
social-buttons.css
557 ms
css
28 ms
style.css
554 ms
jquery-latest.min.js
8 ms
bootstrap.min.js
602 ms
social-buttons.js
622 ms
jquery.lazyloadxt.js
627 ms
dialogize.js
790 ms
cookieconsent.js
732 ms
sdk.js
59 ms
fontawesome-webfont.woff
217 ms
7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf
49 ms
anMUvcNT0H1YN4FII8wprzsSLeNQG2cy_mKit6iEdYs.ttf
51 ms
oikonomiki2.jpg
145 ms
www.kamikaze.gr.jpg
159 ms
tsoukalas_takis708.jpg
149 ms
2102.png
410 ms
3c59dc048e8850243be8079a5c74d079-162.jpg
230 ms
deite-sillogi-entiposiakes-fotografies-travixtikan-katallili-stigmi.jpg
253 ms
ArticleImage_224279-jpg.xpng
899 ms
kamikazi%2B%25281%2529.jpg
142 ms
Giannis-Boutaris.jpg
200 ms
k15.jpg
29 ms
atm.jpg
29 ms
9313-810x425.jpg
366 ms
855558888-810x423.png
369 ms
71 ms
xd_arbiter.php
37 ms
xd_arbiter.php
49 ms
dark-top.css
17 ms
was.gr accessibility score
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
Document doesn't have a <title> element
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
was.gr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
was.gr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Was.gr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Was.gr 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.
was.gr
Open Graph data is detected on the main page of Was. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: