4.6 sec in total
868 ms
3.2 sec
529 ms
Visit eyxes.gr now to see the best up-to-date Eyxes content and also check out these interesting facts you probably never knew about eyxes.gr
Visit eyxes.grWe analyzed Eyxes.gr page load time and found that the first response time was 868 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
eyxes.gr performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value17.3 s
0/100
25%
Value9.6 s
11/100
10%
Value780 ms
37/100
30%
Value0.023
100/100
15%
Value11.2 s
19/100
10%
868 ms
181 ms
270 ms
192 ms
184 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 94% of them (87 requests) were addressed to the original Eyxes.gr, 5% (5 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (868 ms) belongs to the original domain Eyxes.gr.
Page size can be reduced by 493.8 kB (25%)
2.0 MB
1.5 MB
In fact, the total size of Eyxes.gr main page is 2.0 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.4 MB which makes up the majority of the site volume.
Potential reduce by 32.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 32.0 kB or 81% of the original size.
Potential reduce by 73.8 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. Eyxes images are well optimized though.
Potential reduce by 209.3 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 209.3 kB or 71% of the original size.
Potential reduce by 178.7 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. Eyxes.gr needs all CSS files to be minified and compressed as it can save up to 178.7 kB or 82% of the original size.
Number of requests can be reduced by 41 (47%)
87
46
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyxes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
eyxes.gr
868 ms
nextgen_gallery_related_images.css
181 ms
font-awesome.css
270 ms
slideshow.css
192 ms
style.css
184 ms
css
24 ms
style.css
186 ms
content-sidebar.css
189 ms
jquery.bxslider.css
270 ms
bootstrap.min.css
541 ms
main.css
363 ms
nivo-lightbox.css
274 ms
default.css
279 ms
colorbox.css
352 ms
ajax.js
353 ms
jquery.js
636 ms
jquery-migrate.min.js
372 ms
persist.js
528 ms
store.js
441 ms
ngg_store.js
451 ms
lightbox_context.js
465 ms
jquery.timeago.js
529 ms
hoverIntent.min.js
551 ms
superfish.js
561 ms
bootstrap.min.js
706 ms
nivo-lightbox.min.js
619 ms
bxslider.js
623 ms
custom.js
634 ms
coin-slider.js
657 ms
jquery.colorbox.js
797 ms
jquery.tooltip.js
712 ms
lightbox-gallery.js
723 ms
gallery.js
725 ms
lightbox-gallery.css
847 ms
trigger_buttons.css
793 ms
nextgen_basic_thumbnails.css
815 ms
style.css
738 ms
nggallery.css
717 ms
slideshow.js
806 ms
navigation.js
731 ms
skip-link-focus-fix.js
733 ms
common.js
768 ms
nextgen_basic_thumbnails.js
718 ms
font-awesome.min.css
687 ms
579 ms
IMGP0171-290x195.jpg
98 ms
IMGP0105-290x195.jpg
91 ms
IMGP0097-290x195.jpg
148 ms
IMGP0037-290x195.jpg
165 ms
thumbs_imgp0054-1024x768.jpg
176 ms
thumbs_imgp0091.jpg
181 ms
thumbs_imgp0102.jpg
194 ms
thumbs_imgp00501.jpg
239 ms
thumbs_ok4imgp0053.jpg
256 ms
IMGP0171-725x400.jpg
355 ms
601 ms
692 ms
767 ms
cropped-ok-banner.png
845 ms
IMGP0217-150x150.jpg
93 ms
IMGP0197-150x150.jpg
93 ms
IMGP0186-150x150.jpg
182 ms
IMGP01711-150x150.jpg
185 ms
IMGP0166-150x150.jpg
272 ms
IMGP0008-150x150.jpg
278 ms
%CE%B2%CE%B1%CF%80%CF%84%CE%B9%CF%83%CE%B7-012-150x150.jpg
295 ms
%CF%83%CE%AC%CF%81%CF%89%CF%83%CE%B70003-150x150.jpg
361 ms
%CE%B2%CE%B1%CF%80%CF%84%CE%B9%CF%83%CE%B7-011-150x150.jpg
370 ms
%CE%B2%CE%B1%CF%80%CF%84%CE%B9%CF%83%CE%B7-008-150x150.jpg
386 ms
%CE%B2%CE%B1%CF%80%CF%84%CE%B9%CF%83%CE%B7-007-150x150.jpg
438 ms
%CE%B2%CE%B1%CF%80%CF%84%CE%B9%CF%83%CE%B7-001-150x150.jpg
452 ms
IMGP0106-300x225.jpg
461 ms
IMGP0107-300x225.jpg
477 ms
papoutsakia-agori-vaptish-1-small-300x225.jpg
584 ms
papoutsakia-agori-vaptish-2-small-300x225.jpg
504 ms
IMGP0077SS-300x225.jpg
541 ms
IMGP0082SS-300x225.jpg
552 ms
IMGP0084SS-300x225.jpg
565 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
8 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
17 ms
PIbvSEyHEdL91QLOQRnZ14nF5uFdDttMLvmWuJdhhgs.ttf
16 ms
LeFlHvsZjXu2c3ZRgBq9nKCWcynf_cDxXwCLxiixG1c.ttf
34 ms
fontawesome-webfont.woff
669 ms
fontawesome-webfont.woff
604 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
17 ms
bx_loader.gif
211 ms
IMGP0171-290x195.jpg
311 ms
IMGP0105-290x195.jpg
240 ms
IMGP0097-290x195.jpg
290 ms
IMGP0037-290x195.jpg
302 ms
overlay.png
333 ms
border.png
361 ms
controls.png
381 ms
eyxes.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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eyxes.gr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
eyxes.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
EL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyxes.gr 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 Eyxes.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.
eyxes.gr
Open Graph description is not detected on the main page of Eyxes. 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: