6.2 sec in total
895 ms
4.4 sec
893 ms
Click here to check amazing AMFISSAFACE content for Greece. Otherwise, check out these important facts you probably never knew about amfissaface.gr
Visit amfissaface.grWe analyzed Amfissaface.gr page load time and found that the first response time was 895 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
amfissaface.gr performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value9.3 s
1/100
25%
Value8.0 s
22/100
10%
Value170 ms
92/100
30%
Value0
100/100
15%
Value10.4 s
24/100
10%
895 ms
261 ms
185 ms
185 ms
186 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 75% of them (71 requests) were addressed to the original Amfissaface.gr, 9% (9 requests) were made to Fonts.gstatic.com and 7% (7 requests) were made to Amfissaface.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Amfissaface.gr.
Page size can be reduced by 653.3 kB (23%)
2.8 MB
2.1 MB
In fact, the total size of Amfissaface.gr main page is 2.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. 70% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 103.9 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 18.0 kB, which is 14% 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 103.9 kB or 83% of the original size.
Potential reduce by 97.2 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. AMFISSAFACE images are well optimized though.
Potential reduce by 336.7 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 336.7 kB or 71% of the original size.
Potential reduce by 115.5 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. Amfissaface.gr needs all CSS files to be minified and compressed as it can save up to 115.5 kB or 82% of the original size.
Number of requests can be reduced by 33 (43%)
77
44
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AMFISSAFACE. 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 15 to 1 for CSS and as a result speed up the page load time.
www.amfissaface.gr
895 ms
wp-emoji-release.min.js
261 ms
overlay-basic.css
185 ms
styles.css
185 ms
styles.css
186 ms
style.css
224 ms
css
63 ms
normalize.css
582 ms
style.css
274 ms
font-awesome.min.css
366 ms
jquery.bxslider.css
276 ms
responsive.css
313 ms
slicknav.css
351 ms
jquery.js
638 ms
jquery-migrate.min.js
366 ms
q2w3-fixed-widget.min.js
404 ms
jquery.tools.min.wp-front.v3.js
632 ms
flexslider.css
392 ms
public.css
395 ms
plugin.css
431 ms
jquery.form.min.js
484 ms
scripts.js
488 ms
modernizr.js
524 ms
jquery.fitvids.js
576 ms
jquery.bxslider.min.js
670 ms
burnhambox-bx.js
607 ms
burnhambox.js
615 ms
jquery.slicknav.min.js
660 ms
wp-embed.min.js
662 ms
jquery.flexslider-min.js
916 ms
jquery.touchSwipe.min.js
701 ms
jquery.easing.1.3.js
706 ms
ditty-news-ticker.js
754 ms
style.css
644 ms
splash_header.jpg
948 ms
MXE4DyLq_normal.jpg
605 ms
logo.png
948 ms
banner_head_01.jpg
946 ms
01_asimina.jpg
951 ms
02_karabasis.jpg
976 ms
05_skokas.jpg
979 ms
03a_charmaina.jpg
1038 ms
Refugees-1200x500-600x400.jpg
751 ms
09-600x400.jpg
746 ms
Asteras02-1200x500-600x400.jpg
791 ms
Skaribas-1200x500-600x400.jpg
752 ms
Nosokomeio2-1200x500-600x400.jpg
750 ms
Elaionas-1200x500-600x400.jpg
940 ms
Epsfokidas-1200x500-600x400.jpg
1035 ms
Anakyklosi-1200x500-600x400.jpg
1021 ms
Stoixeio01-1200x500-600x400.jpg
1020 ms
10-600x400.jpg
1118 ms
07a_vinias-342x300.jpg
891 ms
06_bookstore-342x300.jpg
1068 ms
14_segditsas-342x300.jpg
1099 ms
11_iqstore-342x300.jpg
1111 ms
DSC_0046-600x400.jpg
1202 ms
Ppe21-1200%CF%87500-600x400.jpg
1223 ms
Kypelloeps-1200x500-600x400.jpg
1259 ms
Ppe21_1200x500-600x400.jpg
1282 ms
Mantoubalos-1200X500-600x400.jpg
1293 ms
08a_bahalo-342x300.jpg
1213 ms
10_carwash-342x300.jpg
1295 ms
12_silvia-342x300.jpg
1306 ms
09_stavedo-342x300.jpg
1319 ms
Prosfiges-1200x500.jpg
1438 ms
Forum-1200x500.jpg
1453 ms
fJwKFYo9XEsYeVx86yVYiKCWcynf_cDxXwCLxiixG1c.ttf
540 ms
wLvvkEcZMKy95afLWh2EfNqQynqKV_9Plp7mupa0S4g.ttf
686 ms
-UtkePo3NFvxEN3rGCtTvtqQynqKV_9Plp7mupa0S4g.ttf
824 ms
fontawesome-webfont.woff
1508 ms
rPYmlwqWyhpKafoxVocSUfesZW2xOQ-xsNqO47m55DA.ttf
726 ms
Iiwv6KObr74zijHv9BX0bA.ttf
758 ms
b31S45a_TNgaBApZhTgE6C3USBnSvpkopQaUR-2r7iU.ttf
827 ms
Foydq9xJp--nfYIx2TBz9bOLyRJkM5aLlPlkJMOAyH0.ttf
826 ms
lyvcXAp_ih3ehVX3UeaIavesZW2xOQ-xsNqO47m55DA.ttf
822 ms
QABk9IxT-LFTJ_dQzv7xpF02b4v3fUxqf9CZJ1qUoIA.ttf
826 ms
sdk.js
23 ms
analytics.js
506 ms
bx_loader.gif
791 ms
btn-prev.png
805 ms
btn-next.png
818 ms
close.png
882 ms
collect
157 ms
bg_direction_nav.png
765 ms
260 ms
xd_arbiter.php
79 ms
xd_arbiter.php
153 ms
splash_header.jpg
768 ms
banner_head_01.jpg
703 ms
logo.png
618 ms
01_asimina.jpg
812 ms
02_karabasis.jpg
755 ms
05_skokas.jpg
860 ms
03a_charmaina.jpg
814 ms
amfissaface.gr accessibility score
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
amfissaface.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
amfissaface.gr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Amfissaface.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 Amfissaface.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.
amfissaface.gr
Open Graph description is not detected on the main page of AMFISSAFACE. 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: