5.5 sec in total
361 ms
4.5 sec
545 ms
Welcome to pkz.ch homepage info - get ready to check PKZ best content for Switzerland right away, or after learning these important things about pkz.ch
Shoppen Sie im Online Shop von PKZ bereits heute die Looks von Morgen. Jetzt online Herren- und Damenbekleidung shoppen und von kostenlosem Versand profitieren!
Visit pkz.chWe analyzed Pkz.ch page load time and found that the first response time was 361 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
pkz.ch performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value15.9 s
0/100
25%
Value12.2 s
3/100
10%
Value1,350 ms
17/100
30%
Value0.523
15/100
15%
Value12.3 s
15/100
10%
361 ms
707 ms
1129 ms
696 ms
81 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 33% of them (31 requests) were addressed to the original Pkz.ch, 33% (31 requests) were made to Imgsrv.pkz.ch and 14% (13 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Imgsrv.pkz.ch.
Page size can be reduced by 472.1 kB (17%)
2.8 MB
2.3 MB
In fact, the total size of Pkz.ch 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 164.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. This page needs HTML code to be minified as it can gain 59.1 kB, which is 32% 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 164.3 kB or 90% of the original size.
Potential reduce by 290.9 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. Obviously, PKZ needs image optimization as it can save up to 290.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 15.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 1.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. Pkz.ch has all CSS files already compressed.
Number of requests can be reduced by 22 (29%)
75
53
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PKZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
pkz.ch
361 ms
www.pkz.ch
707 ms
1129 ms
app.js
696 ms
fza7dtm.js
81 ms
app.js
53 ms
gtmhelper.js
92 ms
intlTelInput.css
182 ms
jquery-ui.css
273 ms
styles.css
364 ms
addtocartslider.css
420 ms
behamics.js
78 ms
intlTelInput.min.js
534 ms
jquery.min.js
49 ms
jquery.validate.min.js
64 ms
jquery.validate.unobtrusive.min.js
65 ms
jquery-ui.min.js
728 ms
scripts.js
633 ms
public.common.js
454 ms
rti.min.js
487 ms
api.js
56 ms
ld.js
37 ms
app.css
97 ms
module.js
297 ms
widget
638 ms
bav2.js
929 ms
ch.png
124 ms
0000755193.jpg
878 ms
logo.png
442 ms
logo-small.png
441 ms
leaf.png
441 ms
insidercard-de.png
440 ms
paypal.png
440 ms
klarna.png
440 ms
twint.png
445 ms
visa.png
445 ms
post.png
445 ms
mastercard.png
444 ms
amex.png
444 ms
diners.png
444 ms
applepay.png
581 ms
googlepay.png
581 ms
0000755189.jpg
833 ms
0000755195.jpg
865 ms
0000755190.jpg
832 ms
0000755194.jpg
831 ms
0000755191.jpg
865 ms
0000755197.jpg
933 ms
0000746369.jpg
932 ms
0000752927.jpg
1112 ms
0000754533.jpg
1011 ms
0000754974.jpg
1024 ms
0000739593.jpg
1119 ms
0000739984.jpg
1118 ms
00742603_732213_fuchsia_front.415.jpg
1116 ms
st_01283813.415.jpg
1110 ms
00743044_632525_rosa_front.415.jpg
1118 ms
00748317_533109_pink_front.415.jpg
1203 ms
00740481_533110_marine_flat.415.png
1293 ms
00740482_533111_schwarz_flat.415.png
1299 ms
00749840_548914_pink_front.415.jpg
1211 ms
00753907_548913_schwarz_front.415.jpg
1213 ms
00743020_632485_fuchsia_front.415.jpg
1207 ms
00745869_751932_pink_front.415.jpg
1294 ms
00741374_632441_fuchsia_front.415.jpg
1301 ms
00741022_632524_pink_front.415.jpg
1303 ms
00743998_632523_weiss_front.415.jpg
1303 ms
00735163_533095_rot_front.415.jpg
1384 ms
00745547_533096_pink_front.415.jpg
1386 ms
00753221_533094_mittelblau_front.415.jpg
1391 ms
00746005_833530_rosa_front.415.jpg
1393 ms
00750902_533116_pink_front.415.jpg
1394 ms
ElegantIcons.woff
547 ms
icomoon.ttf
466 ms
recaptcha__de.js
329 ms
insider-card.png
497 ms
tile2.png
426 ms
i
176 ms
i
196 ms
i
199 ms
i
197 ms
i
197 ms
i
197 ms
i
198 ms
i
197 ms
i
303 ms
i
292 ms
i
303 ms
i
297 ms
settings-icon
236 ms
syncframe
188 ms
consent
347 ms
v2
192 ms
event
341 ms
details
194 ms
pkz.ch 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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes are not valid or misspelled
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
pkz.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pkz.ch SEO score
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
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pkz.ch can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pkz.ch 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.
pkz.ch
Open Graph description is not detected on the main page of PKZ. 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: