3.9 sec in total
369 ms
3.2 sec
257 ms
Welcome to pez.at homepage info - get ready to check PEZ best content for Greece right away, or after learning these important things about pez.at
PEZ
Visit pez.atWe analyzed Pez.at page load time and found that the first response time was 369 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pez.at performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value3.9 s
51/100
25%
Value9.9 s
10/100
10%
Value260 ms
83/100
30%
Value0.09
92/100
15%
Value4.6 s
81/100
10%
369 ms
503 ms
213 ms
577 ms
25 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 64% of them (49 requests) were addressed to the original Pez.at, 13% (10 requests) were made to Static.xx.fbcdn.net and 12% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Pez.at.
Page size can be reduced by 194.0 kB (23%)
840.3 kB
646.3 kB
In fact, the total size of Pez.at main page is 840.3 kB. 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 630.1 kB which makes up the majority of the site volume.
Potential reduce by 22.4 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 22.4 kB or 73% of the original size.
Potential reduce by 48.1 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. PEZ images are well optimized though.
Potential reduce by 107.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 107.7 kB or 68% of the original size.
Potential reduce by 15.8 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. Pez.at needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 79% of the original size.
Number of requests can be reduced by 10 (13%)
75
65
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PEZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
pez.at
369 ms
PEZ-Home
503 ms
bde782ee382c58e84d39ed90ec9a39d0.css
213 ms
b78319b9e39686c3efee9dd71f4e2377.js
577 ms
all.js
25 ms
body_bg.png
108 ms
1.png
109 ms
2.png
110 ms
3.png
215 ms
4.png
223 ms
5.png
219 ms
6.png
216 ms
7.png
223 ms
8.png
220 ms
9.png
319 ms
10.png
320 ms
11.png
321 ms
12.png
322 ms
13.png
323 ms
logo.png
323 ms
overlay_white.png
425 ms
c5ea908b31c4afcbc7b2262224854661.jpg
1389 ms
candy_1.png
428 ms
candy_2.png
533 ms
label_onlinebefragung.png
531 ms
header_bg_schatten.png
431 ms
news.png
530 ms
candy_3.png
851 ms
c8eb93586a81db26e773ba32b8fa9e24.jpg
750 ms
aabeff858bdb5e192b3f11676f7cd9d1.jpg
1068 ms
de04356005837c7e0703c7d2e975627a.jpg
853 ms
f5898c8bde1bd3b3d614b0497134d331.jpg
969 ms
2c01f83f5ee41f8f4c728e7de3397721.jpg
968 ms
1f163489b39e6600cb52cee1af1a6397.jpg
1186 ms
news_video_overlay.png
965 ms
newsselector.png
1071 ms
04fe4a5b330dcc12fe59ffb183a20ef8.jpg
1075 ms
df84a926e54f8de6b43a80e317b0c8e9.jpg
1077 ms
dbe631775ff1ebb01a87163fcc23ecce.jpg
1293 ms
facebook.png
1190 ms
t.js
440 ms
twitter.png
1184 ms
238 ms
xd_arbiter.php
43 ms
xd_arbiter.php
49 ms
b_log2.png
1089 ms
Level0SubArrow.png
1186 ms
shop_icon.png
1190 ms
de.png
1087 ms
en.png
1087 ms
fr.png
1184 ms
es.png
1185 ms
search_arrows.png
1185 ms
footer_icons.png
1186 ms
cnt_js.php
268 ms
cntcc
274 ms
ping
160 ms
like_box.php
302 ms
hDvwL1_H7g-.css
36 ms
56WNbrUYLbL.css
39 ms
q68gy-v_YMF.js
38 ms
FJmpeSpHpjS.js
56 ms
0wM5s1Khldu.js
32 ms
1bNoFZUdlYZ.js
63 ms
12417624_976129622422645_1137795248313074839_n.jpg
50 ms
10801758_803401919695417_2431996126763096005_n.jpg
18 ms
426254_3820306628382_879389450_n.jpg
19 ms
12246962_10153692388635629_2694585889132237091_n.jpg
22 ms
11078071_1084820234867885_2361469241419800017_n.jpg
21 ms
12004036_398450280352241_4457737308070180151_n.jpg
48 ms
1914663_10208576798121846_4601547572254131088_n.jpg
22 ms
1934063_910828845701447_825474995109436973_n.jpg
21 ms
10590614_277478185791989_696754750000383609_n.jpg
22 ms
wL6VQj7Ab77.png
16 ms
s7jcwEQH7Sx.png
15 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
6 ms
pez.at 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
Image elements do not have [alt] attributes
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
pez.at 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
Missing source maps for large first-party JavaScript
pez.at 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pez.at 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 Pez.at 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.
pez.at
Open Graph description is not detected on the main page of PEZ. 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: