10.6 sec in total
2 sec
8.2 sec
416 ms
Welcome to y-o.gr homepage info - get ready to check Y O best content for Greece right away, or after learning these important things about y-o.gr
Ενημέρωση για την υγεία, την ομορφιά, τη διατροφή, την πρόληψη, τη θεραπεία, τη δίαιτα, το σεξ, την ευεξία, το lifestyle και το fitness για όλη την οικογένεια.
Visit y-o.grWe analyzed Y-o.gr page load time and found that the first response time was 2 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
y-o.gr performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value25.2 s
0/100
25%
Value14.5 s
1/100
10%
Value3,240 ms
2/100
30%
Value0.042
99/100
15%
Value29.0 s
0/100
10%
1980 ms
377 ms
369 ms
392 ms
415 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 96% of them (72 requests) were addressed to the original Y-o.gr, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Cdn-images.mailchimp.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Y-o.gr.
Page size can be reduced by 818.6 kB (37%)
2.2 MB
1.4 MB
In fact, the total size of Y-o.gr main page is 2.2 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. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 34.1 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 34.1 kB or 79% of the original size.
Potential reduce by 166.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. Obviously, Y O needs image optimization as it can save up to 166.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 391.8 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 391.8 kB or 69% of the original size.
Potential reduce by 226.3 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. Y-o.gr needs all CSS files to be minified and compressed as it can save up to 226.3 kB or 83% of the original size.
Number of requests can be reduced by 49 (67%)
73
24
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Y O. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
y-o.gr
1980 ms
modal.css
377 ms
k2.css
369 ms
font-awesome.css
392 ms
normalize.css
415 ms
layout.css
373 ms
joomla.css
426 ms
system.css
784 ms
template.css
793 ms
menu.css
799 ms
gk.stuff.css
795 ms
style1.css
807 ms
style1.css
822 ms
style.css
1178 ms
bootstrap.min.css
1203 ms
jquery.min.js
1291 ms
jquery-noconflict.js
1198 ms
jquery-migrate.min.js
1230 ms
bootstrap.min.js
1562 ms
mootools-core.js
1666 ms
core.js
1591 ms
mootools-more.js
1741 ms
modal.js
1623 ms
modernizr.js
1686 ms
gk.scripts.js
1952 ms
gk.menu.js
1985 ms
fitvids.jquery.js
2004 ms
engine.mootools.js
2041 ms
engine.jquery.js
2072 ms
override.css
2118 ms
asyncjs.php
1119 ms
classic-081711.css
4 ms
analytics.js
7 ms
logo.jpg
413 ms
rss-icon.png
578 ms
healthy_site2.jpg
1005 ms
health_beauty.jpg
706 ms
fontawesome-webfont.woff
580 ms
collect
14 ms
asyncspc.php
567 ms
ac801a110649bf56dcaa67ddf2e03ea9.jpg
655 ms
lg.php
486 ms
4e8fc9a3348d8449a1091dd4e3cca884.jpg
566 ms
lg.php
489 ms
d91e56018994620efa5f6ba86bdd1f79.jpg
879 ms
lg.php
560 ms
c74930d02788400c22b5f07690002b2a.jpg
977 ms
lg.php
881 ms
42dc0a1630d791ed1f74a43c095e000a.gif
1357 ms
lg.php
983 ms
efec6d388900fb732c67e3f62b18d2b4.jpg
1255 ms
lg.php
1334 ms
659df18259465745a2c54f7997cd3b8d.jpg
1636 ms
lg.php
1430 ms
e4cca33235287ede907dc74ac9e435ca.jpg
1519 ms
lg.php
1706 ms
f51e2e71e0ac8e81b8785ab73e012555.jpg
1890 ms
lg.php
1844 ms
957834781584d25004bd8366d515374f.jpg
1914 ms
lg.php
1993 ms
927099a4ed62b5b1032dc1cb69a2e9f7.jpg
2208 ms
lg.php
2134 ms
a3dfa0561587beb803a9701fa11ed7a2.jpg
2405 ms
lg.php
2322 ms
bd7189d38004e7e25d82145d7180a5dd.jpg
2318 ms
lg.php
2500 ms
907e78bd3b418eb555fd644a8c229440.gif
3033 ms
lg.php
2667 ms
0d6a230bbd53cfa682aed802c12ec837.jpg
2851 ms
lg.php
2798 ms
small.desktop.css
418 ms
tablet.css
405 ms
small.tablet.css
402 ms
mobile.css
411 ms
logo_small1.png
384 ms
y-o.gr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
y-o.gr 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
y-o.gr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Y-o.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it matches the claimed language. Our system also found out that Y-o.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.
y-o.gr
Open Graph description is not detected on the main page of Y O. 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: