3.2 sec in total
523 ms
2.4 sec
303 ms
Visit antidot.gr now to see the best up-to-date Antidot content and also check out these interesting facts you probably never knew about antidot.gr
A multidisciplinary design studio, specialising in digital and communication design. We advocate Design Thinking and are open to collaborations and subcontracting.
Visit antidot.grWe analyzed Antidot.gr page load time and found that the first response time was 523 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
antidot.gr performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value21.8 s
0/100
25%
Value12.4 s
3/100
10%
Value3,650 ms
1/100
30%
Value0.075
95/100
15%
Value23.0 s
1/100
10%
523 ms
192 ms
346 ms
191 ms
268 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 88% of them (38 requests) were addressed to the original Antidot.gr, 5% (2 requests) were made to S7.addthis.com and 5% (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 Antidot.gr.
Page size can be reduced by 497.0 kB (28%)
1.8 MB
1.3 MB
In fact, the total size of Antidot.gr main page is 1.8 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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 42.0 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 42.0 kB or 68% of the original size.
Potential reduce by 103.6 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. Antidot images are well optimized though.
Potential reduce by 328.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 328.9 kB or 64% of the original size.
Potential reduce by 22.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. Antidot.gr needs all CSS files to be minified and compressed as it can save up to 22.4 kB or 85% of the original size.
Number of requests can be reduced by 20 (48%)
42
22
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Antidot. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
antidot.gr
523 ms
swfobject.js
192 ms
jquery.js
346 ms
jquery.mousewheel.js
191 ms
jScrollPane.js
268 ms
animatedcollapse.js
206 ms
style.css
275 ms
addthis_widget.js
14 ms
ga.js
135 ms
header_back.jpg
217 ms
antidotdesignstudio.png
206 ms
m_104_el.png
216 ms
m_105_el.png
223 ms
m_106_el.png
204 ms
m_107_el.png
223 ms
m_110_el.png
377 ms
m_138_el.png
379 ms
m_138_en.png
411 ms
top_arrow_f8f8f8.png
416 ms
box_top_w900.png
425 ms
box_bottom_w900.png
426 ms
box_back_w900.png
538 ms
a_860_161_el.png
550 ms
b_1404_or_880x438-template-for-website---autumn15.jpg
835 ms
b_1405_or_880x438-template-for-website---autumn15-b.jpg
757 ms
b_1382_or_detroit1.jpg
1153 ms
b_1383_or_detroit2.jpg
1078 ms
b_1394_or_880x438-amnesty-logo-01index.jpg
861 ms
thumb.png
711 ms
main_1420_880x580-utopia_1.jpg
953 ms
main_1412_880x580-odyssey.jpg
995 ms
main_1407_aaaa.jpg
1083 ms
main_1410_bbbb.jpg
1038 ms
main_1390_880x580-amnesty-thumb.jpg
1115 ms
more_projects_el.png
1155 ms
top_el.png
1213 ms
footer.jpg
1472 ms
300lo.json
76 ms
gradient_100.jpg
1132 ms
gradient_500.jpg
1156 ms
gradient_400.jpg
1186 ms
sh.8e5f85691f9aaa082472a194.html
62 ms
__utm.gif
38 ms
antidot.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
Buttons do not have an accessible name
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
antidot.gr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
antidot.gr 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
EN
EL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Antidot.gr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Greek language. Our system also found out that Antidot.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.
antidot.gr
Open Graph description is not detected on the main page of Antidot. 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: