6.7 sec in total
1.1 sec
5.2 sec
350 ms
Visit prestige.gr now to see the best up-to-date Prestige content and also check out these interesting facts you probably never knew about prestige.gr
Visit prestige.grWe analyzed Prestige.gr page load time and found that the first response time was 1.1 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
prestige.gr performance score
name
value
score
weighting
Value7.6 s
1/100
10%
Value7.7 s
3/100
25%
Value14.9 s
1/100
10%
Value910 ms
31/100
30%
Value0.004
100/100
15%
Value13.9 s
10/100
10%
1094 ms
50 ms
161 ms
178 ms
252 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 98% of them (104 requests) were addressed to the original Prestige.gr, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Prestige.gr.
Page size can be reduced by 810.2 kB (54%)
1.5 MB
687.9 kB
In fact, the total size of Prestige.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. 65% of websites need less resources to load. CSS take 617.5 kB which makes up the majority of the site volume.
Potential reduce by 34.3 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.3 kB or 78% of the original size.
Potential reduce by 666 B
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. Prestige images are well optimized though.
Potential reduce by 258.0 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 258.0 kB or 75% of the original size.
Potential reduce by 517.2 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. Prestige.gr needs all CSS files to be minified and compressed as it can save up to 517.2 kB or 84% of the original size.
Number of requests can be reduced by 99 (95%)
104
5
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prestige. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 60 to 1 for CSS and as a result speed up the page load time.
1094 ms
css
50 ms
grid.css
161 ms
base.css
178 ms
layout.css
252 ms
audio-player.css
198 ms
blog.css
203 ms
postslider.css
153 ms
buttons.css
182 ms
buttonrow.css
203 ms
buttons_fullwidth.css
232 ms
catalogue.css
203 ms
comments.css
288 ms
contact.css
343 ms
slideshow.css
316 ms
contentslider.css
297 ms
countdown.css
311 ms
gallery.css
331 ms
gallery_horizontal.css
337 ms
google_maps.css
436 ms
grid_row.css
435 ms
heading.css
431 ms
headline_rotator.css
395 ms
hr.css
371 ms
icon.css
373 ms
iconbox.css
502 ms
iconlist.css
498 ms
image.css
499 ms
image_hotspots.css
499 ms
magazine.css
464 ms
masonry_entries.css
472 ms
avia-snippet-site-preloader.css
540 ms
menu.css
518 ms
notification.css
536 ms
numbers.css
512 ms
portfolio.css
499 ms
progressbar.css
494 ms
promobox.css
531 ms
slideshow_accordion.css
407 ms
slideshow_feature_image.css
394 ms
slideshow_fullsize.css
387 ms
slideshow_fullscreen.css
382 ms
slideshow_layerslider.css
375 ms
social_share.css
394 ms
tab_section.css
398 ms
table.css
427 ms
tabs.css
376 ms
team.css
351 ms
testimonials.css
363 ms
timeline.css
358 ms
toggles.css
351 ms
video.css
380 ms
style.min.css
393 ms
shortcodes.css
360 ms
magnific-popup.css
350 ms
avia-snippet-lightbox.css
380 ms
avia-snippet-widget.css
317 ms
mediaelementplayer-legacy.min.css
348 ms
wp-mediaelement.min.css
362 ms
enfold.css
421 ms
custom.css
345 ms
jquery.js
418 ms
avia-compat.js
320 ms
avia.js
350 ms
shortcodes.js
404 ms
audio-player.js
402 ms
contact.js
586 ms
slideshow.js
737 ms
countdown.js
739 ms
gallery.js
746 ms
gallery_horizontal.js
745 ms
headline_rotator.js
757 ms
iconlist.js
758 ms
image_hotspots.js
750 ms
magazine.js
748 ms
isotope.js
750 ms
masonry_entries.js
749 ms
menu.js
747 ms
notification.js
746 ms
numbers.js
715 ms
portfolio.js
726 ms
progressbar.js
687 ms
slideshow-video.js
672 ms
slideshow_accordion.js
672 ms
slideshow_fullscreen.js
671 ms
slideshow_layerslider.js
655 ms
tab_section.js
654 ms
tabs.js
619 ms
testimonials.js
602 ms
timeline.js
603 ms
toggles.js
595 ms
video.js
590 ms
jquery.magnific-popup.min.js
597 ms
avia-snippet-lightbox.js
645 ms
avia-snippet-sticky-header.js
645 ms
mediaelement-and-player.min.js
650 ms
mediaelement-migrate.min.js
622 ms
wp-mediaelement.min.js
593 ms
avia_google_maps_front.js
542 ms
wp-embed.min.js
539 ms
wp-emoji-release.min.js
405 ms
Prestige-Logo-1L2.jpg
409 ms
Prestige-Textiles-SA-21-1500x430.jpg
438 ms
Prestige-Textiles-SA-13-1500x430.jpg
429 ms
entypo-fontello.woff
181 ms
analytics.js
174 ms
prestige.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-hidden="true"] elements contain focusable descendents
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.
prestige.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
Issues were logged in the Issues panel in Chrome Devtools
prestige.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prestige.gr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Prestige.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.
prestige.gr
Open Graph description is not detected on the main page of Prestige. 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: