6.3 sec in total
362 ms
5.7 sec
177 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 362 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
pez.at performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value4.6 s
34/100
25%
Value5.3 s
58/100
10%
Value430 ms
65/100
30%
Value0.407
24/100
15%
Value5.3 s
73/100
10%
362 ms
312 ms
374 ms
853 ms
558 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pez.at, 78% (29 requests) were made to Int.pez.com and 8% (3 requests) were made to Mailworx.marketingsuite.info. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Int.pez.com.
Page size can be reduced by 197.7 kB (6%)
3.1 MB
2.9 MB
In fact, the total size of Pez.at main page is 3.1 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. 20% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 77.6 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 77.6 kB or 78% of the original size.
Potential reduce by 118.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. PEZ images are well optimized though.
Potential reduce by 318 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 940 B
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 has all CSS files already compressed.
Number of requests can be reduced by 10 (32%)
31
21
The browser has sent 31 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 5 to 1 for JavaScripts and as a result speed up the page load time.
pez.at
362 ms
Home
312 ms
3f879adb62c4322c2d905396845da4f3.css
374 ms
1179f8c2091eea79c110f3c45f336f42.js
853 ms
e.js
558 ms
t.js
432 ms
logo.png
137 ms
Form
622 ms
pez-bonbons-mars-mission-space-shuttle_4e8d3c3cd0c94be505c114d2b8f0c7c8.png
130 ms
pez-bonbons-hello-kitty-fullbody_4c9671f3c4bb122e361197a3c685c208.png
381 ms
PEZ_Rainbow_Mix_6Pack_EBK_20B12220_WB19_frontal_RGB_d8676db296d9f021b0c5b8e2bd8b1bed.png
347 ms
pez-bonbons-gabbys-dollhouse-gabby_36e0410117ac9936e6c04d7cc480e3dd.png
262 ms
pez-bonbons-mandalorian-r2d2_962de72411663f928b9ea894b6602918.png
635 ms
Marvel_EBK_IronMan_0b83cd00157afd41c8244f592ca9d220.png
642 ms
shop_link.png
382 ms
arrow_down_language.png
385 ms
gb.png
465 ms
de.png
513 ms
fr.png
515 ms
es.png
517 ms
logo_facebook.svg
591 ms
logo_instagram.png
640 ms
logo_youtube.png
642 ms
candy_3.png
650 ms
Grafik_Schult%C3%BCte.png
968 ms
pez-banner-dispenser_bb42d51c89d1982a0a937a9f0166466b.jpg
1161 ms
Icon_slider_icon_weiss.svg
658 ms
arrow395_color4.svg
659 ms
museosanscnd-300-webfont.woff
786 ms
MuseoSans_300-webfont.woff
671 ms
museosanscnd-500-webfont.woff
792 ms
cntcc
527 ms
Form
618 ms
responsive.css
117 ms
form-init.min.js
227 ms
pez-banner-mars-mission_c6155f8bcd97f52c5e64bd5a2f9854f5.jpg
855 ms
pez-myhead-deingesicht-als-pezspender_a60853b86762fc4bb6dfb9aa440bbc2f.png
1597 ms
pez.at 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
Serves images with low resolution
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 data is detected on the main page of PEZ. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: