1.9 sec in total
291 ms
936 ms
720 ms
Click here to check amazing PzG content for United States. Otherwise, check out these important facts you probably never knew about pzg.biz
Visit pzg.bizWe analyzed Pzg.biz page load time and found that the first response time was 291 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
pzg.biz performance score
name
value
score
weighting
Value1.7 s
91/100
10%
Value2.8 s
85/100
25%
Value6.0 s
47/100
10%
Value4,450 ms
1/100
30%
Value0.045
99/100
15%
Value17.0 s
5/100
10%
291 ms
42 ms
46 ms
41 ms
85 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 92% of them (66 requests) were addressed to the original Pzg.biz, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Server2.web-stat.com. The less responsive or slowest element that took the longest time to load (417 ms) belongs to the original domain Pzg.biz.
Page size can be reduced by 79.2 kB (18%)
441.3 kB
362.2 kB
In fact, the total size of Pzg.biz main page is 441.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. 25% of websites need less resources to load. Images take 352.0 kB which makes up the majority of the site volume.
Potential reduce by 43.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. This page needs HTML code to be minified as it can gain 16.7 kB, which is 30% 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 43.4 kB or 79% of the original size.
Potential reduce by 22.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. PzG images are well optimized though.
Potential reduce by 7.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 7.7 kB or 28% of the original size.
Potential reduce by 5.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. Pzg.biz needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 78% of the original size.
Number of requests can be reduced by 12 (17%)
71
59
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PzG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
pzg.biz
291 ms
expando.js
42 ms
styles.css
46 ms
ga.js
41 ms
safe_subscribe_logo.gif
85 ms
pzg_head-wrap-bg.jpg
98 ms
pzg_logo.jpg
97 ms
pzg_topimage.jpg
146 ms
pzg_content-faux-column.jpg
96 ms
axis_b1.gif
100 ms
pzg_top-menu-title.jpg
100 ms
li-dot.png
146 ms
li-dot.png
147 ms
pzg_sub-menu-title.jpg
148 ms
dagger_nav.gif
149 ms
new11.gif
151 ms
flag-nazi_button.jpg
185 ms
flag_betsyross_button.jpg
186 ms
v709_adolf_hitlerstrasse_but.jpg
186 ms
zyklon_b_sm.jpg
191 ms
pzg_banner_free_speech.jpg
196 ms
sale.gif
191 ms
pzg_banner_panzerwagenlied.jpg
226 ms
pzg_banner_mugs.jpg
279 ms
pzg_banner_sscds.jpg
270 ms
pzg_donation.jpg
240 ms
jesus_fish.gif
237 ms
credit_cards.jpg
235 ms
cc_sm_tested_pci2.gif
266 ms
cc_ccsafe_check3.gif
287 ms
germ-shp_walking.gif
291 ms
barb_wire.gif
290 ms
german_shepard_dog_sniff_bag_md
388 ms
switch_plate_cover_web.jpg
336 ms
pzg_only.gif
330 ms
cart_add.jpg
331 ms
cart_view.jpg
336 ms
f12_hitler_youth_flag.jpg
339 ms
f27_ss_lah_panzer_flag.jpg
372 ms
f09_danzig_flag.jpg
375 ms
log6.js
135 ms
daggers_hy.jpg
362 ms
__utm.gif
28 ms
new06.gif
297 ms
GRR937.jpg
299 ms
GRR938.jpg
327 ms
GRR919.jpg
369 ms
GRR912.jpg
389 ms
hilter_youth_group.jpg
331 ms
275p_Panzer.jpg
348 ms
205p.jpg
306 ms
208p.jpg
327 ms
group_tshirts.jpg
347 ms
book_mein_kampf_ford.jpg
403 ms
count6.pl
97 ms
cal16-02_weltkrieg.jpg
332 ms
mug038_adolf_hitler_victory_med.jpg
332 ms
pzg_mail_1.jpg
349 ms
boots.jpg
362 ms
cd280_cover_med.jpg
367 ms
cd290_cover_med.jpg
379 ms
cd300_ss_schutzstaffel_med.jpg
348 ms
new_bl.gif
340 ms
german_panzer_cruising_md_clr.g
417 ms
michael_hat_shirt.jpg
416 ms
web_stat_wix3.png
120 ms
f05_nsdap_flag.jpg
339 ms
book_mein_kampf_verlag_med.jpg
354 ms
daggers_hy_med.jpg
347 ms
pzg_footer-bg.jpg
336 ms
pzg_eagle_web.jpg
352 ms
envelope.gif
367 ms
pzg.biz accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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>).
pzg.biz 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
Registers an unload listener
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pzg.biz 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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pzg.biz can be misinterpreted by Google and other search engines. Our service has detected that English 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 Pzg.biz main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
pzg.biz
Open Graph description is not detected on the main page of PzG. 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: