5.5 sec in total
931 ms
3.8 sec
729 ms
Welcome to peterpfeiffer.info homepage info - get ready to check Peter Pfeiffer best content right away, or after learning these important things about peterpfeiffer.info
Dein kreativer Kameramann und Fotograf aus Berlin. Du suchst nach einem Multitalent ? Dann sollten wir uns unbedingt unterhalten.
Visit peterpfeiffer.infoWe analyzed Peterpfeiffer.info page load time and found that the first response time was 931 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
peterpfeiffer.info performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value8.4 s
2/100
25%
Value10.1 s
9/100
10%
Value120 ms
97/100
30%
Value1.174
1/100
15%
Value8.1 s
41/100
10%
931 ms
25 ms
198 ms
216 ms
215 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 58% of them (66 requests) were addressed to the original Peterpfeiffer.info, 4% (4 requests) were made to Fls-eu.amazon-adsystem.com and 4% (4 requests) were made to Ecx.images-amazon.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Banners.webmasterplan.com.
Page size can be reduced by 624.2 kB (52%)
1.2 MB
581.0 kB
In fact, the total size of Peterpfeiffer.info main page is 1.2 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. 60% of websites need less resources to load. Javascripts take 615.3 kB which makes up the majority of the site volume.
Potential reduce by 63.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 63.3 kB or 78% of the original size.
Potential reduce by 21.4 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. Peter Pfeiffer images are well optimized though.
Potential reduce by 435.6 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 435.6 kB or 71% of the original size.
Potential reduce by 103.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. Peterpfeiffer.info needs all CSS files to be minified and compressed as it can save up to 103.8 kB or 80% of the original size.
Number of requests can be reduced by 66 (61%)
108
42
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Peter Pfeiffer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.peterpfeiffer.info
931 ms
css
25 ms
style.css
198 ms
jquery.fancybox-1.3.4.css
216 ms
page_templates.css
215 ms
shadowbox.css
217 ms
extras.css
215 ms
polls-css.css
216 ms
shortcodes.css
288 ms
codebox.css
298 ms
jquery.js
403 ms
jquery-migrate.min.js
320 ms
et_shortcodes_frontend.js
318 ms
codebox.js
333 ms
audio-player.js
386 ms
buttons.js
7 ms
trigger_buttons.min.css
390 ms
font-awesome.min.css
454 ms
nextgen_basic_singlepic.min.css
452 ms
nextgen_basic_thumbnails.min.css
457 ms
style.min.css
483 ms
nggallery.css
483 ms
show_ads.js
7 ms
view.asp
337 ms
jquery-ui.min.js
13 ms
jquery.cycle.all.min.js
561 ms
jquery.easing.1.3.js
492 ms
superfish.js
492 ms
jquery.lavalamp.1.3.3-min.js
493 ms
a79fab28010c46abe2dd27b49aa2c107.js
559 ms
polls-js.js
562 ms
jquery.easing-1.3.pack.js
563 ms
jquery.fancybox-1.3.4.pack.js
566 ms
et-ptemplates-frontend.js
568 ms
wp-embed.min.js
611 ms
ajax.min.js
592 ms
common.min.js
616 ms
lightbox_context.min.js
615 ms
nextgen_basic_thumbnails.min.js
637 ms
wp-emoji-release.min.js
593 ms
analytics.js
7 ms
collect
39 ms
cm
608 ms
logo.png
352 ms
search_btn.png
349 ms
iphone_kraftstrom_ladeadapter-300x225-7520_184x184.jpg
608 ms
simple-smile.png
606 ms
iphone_kraftstrom_ladeadapter-300x225.jpg
608 ms
angry_seasons-42904_184x184.jpg
614 ms
amazon-510617_184x184.jpg
627 ms
amazon_spam_01-150x150.jpg
613 ms
amazon_spam_02-150x150.jpg
614 ms
iphone_firmware-170654_184x184.jpg
613 ms
angry_birds_rio.jpg-nggid03120-ngg0dyn-240x0x100-00f0w010c010r110f110r010t010.jpg
626 ms
angry_birds-235827_184x184.jpg
626 ms
thumbs_iphone_wallpaper_herbst_00_0.png
631 ms
thumbs_iphone_wallpaper_herbst_01.png
625 ms
thumbs_iphone_wallpaper_herbst_02.jpg
623 ms
thumbs_iphone_wallpaper_herbst_04.jpg
714 ms
thumbs_iphone_wallpaper_herbst_05.jpg
707 ms
thumbs_iphone_wallpaper_herbst_06.jpg
709 ms
badge_macappstore-sm.png
566 ms
view.asp
1129 ms
header_bg.jpg
672 ms
menu-bg.png
677 ms
ca-pub-4278385830278770.js
97 ms
zrt_lookup.html
134 ms
show_ads_impl.js
90 ms
cm
489 ms
dropdown-separator.png
611 ms
menu-bullet.png
691 ms
search.png
692 ms
content-top-bg-alt.png
692 ms
s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff
115 ms
EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff
115 ms
content-bg-alt.png
687 ms
ud234x60.gif
598 ms
cm
470 ms
cm
470 ms
image-overlay.png
633 ms
widget-separator.png
632 ms
widget-title-bg.png
713 ms
sidebar-bullet.png
710 ms
ads
375 ms
content-bottom-bg-alt.png
674 ms
osd.js
9 ms
link-active-bg.png
670 ms
getAllAppDefault.esi
273 ms
1f600.png
211 ms
VXD-257-House-120x90-DE.jpg
97 ms
174 ms
173 ms
DE_Asso_18-7-14_banners_SSD_changes_234x60.gif
30 ms
171 ms
DE_Asso_1-5-15_Banners_for_Prime_120x600.jpg
231 ms
169 ms
WS_160x600.gif
175 ms
badge_macappstore-sm.png
150 ms
getSegment.php
155 ms
checkOAuth.esi
7 ms
t.dhj
23 ms
t.dhj
19 ms
cm
14 ms
s-3271.xgi
10 ms
hbpix
65 ms
5 ms
xrefid.xgi
4 ms
6 ms
pixel
19 ms
2981
21 ms
kw1021_Restposten_PC_234x60_2.gif
847 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
16 ms
buttons.ab966a004186897711de4a5ed256c924.css
10 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
4 ms
peterpfeiffer.info accessibility score
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.
peterpfeiffer.info 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
Browser errors were logged to the console
peterpfeiffer.info 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Peterpfeiffer.info can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Peterpfeiffer.info 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.
peterpfeiffer.info
Open Graph description is not detected on the main page of Peter Pfeiffer. 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: