5 sec in total
465 ms
3.1 sec
1.4 sec
Click here to check amazing Magentoperformance content for Germany. Otherwise, check out these important facts you probably never knew about magentoperformance.de
Performanceprobleme bei Magento erkennen, analysieren und beheben
Visit magentoperformance.deWe analyzed Magentoperformance.de page load time and found that the first response time was 465 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
magentoperformance.de performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
465 ms
293 ms
199 ms
200 ms
198 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 73% of them (29 requests) were addressed to the original Magentoperformance.de, 13% (5 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (532 ms) belongs to the original domain Magentoperformance.de.
Page size can be reduced by 285.9 kB (37%)
781.1 kB
495.1 kB
In fact, the total size of Magentoperformance.de main page is 781.1 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. 35% of websites need less resources to load. Images take 440.0 kB which makes up the majority of the site volume.
Potential reduce by 60.5 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 60.5 kB or 77% of the original size.
Potential reduce by 46.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, Magentoperformance needs image optimization as it can save up to 46.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 143.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 143.7 kB or 65% of the original size.
Potential reduce by 34.9 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. Magentoperformance.de needs all CSS files to be minified and compressed as it can save up to 34.9 kB or 82% of the original size.
Number of requests can be reduced by 25 (74%)
34
9
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Magentoperformance. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.magentoperformance.de
465 ms
style.css
293 ms
my.css
199 ms
wp-syntax.css
200 ms
app.css
198 ms
jquery.js
492 ms
jquery-migrate.min.js
199 ms
smoothscroll.js
295 ms
external-tracking.min.js
295 ms
lib.core.js
204 ms
lib.view.js
527 ms
client.js
297 ms
client.js
301 ms
tag.item.js
301 ms
tag.ui.js
302 ms
handler.image.js
395 ms
css
25 ms
analytics.js
110 ms
logo-klein.png
152 ms
cropped-header-bar.jpg
150 ms
Bildschirmfoto-2014-07-24-um-07.53.32.png
296 ms
xdebug.png
197 ms
varnish-684x1024.png
532 ms
basecom.png
152 ms
magento_performance_hosting.png
295 ms
rss-icon.png
198 ms
twitter-icon.png
199 ms
fb-icon.png
296 ms
googleplus-icon.png
296 ms
style.css
172 ms
css
26 ms
style.css
267 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
23 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
26 ms
cj2hUnSRBhwmSPr9kS589-LrC4Du4e_yfTJ8Ol60xk0.ttf
33 ms
c92rD_x0V1LslSFt3-QEpmsGzsqhEorxQDpu60nfWEc.ttf
33 ms
QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf
34 ms
collect
18 ms
collect
69 ms
collect
6 ms
magentoperformance.de 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
Document doesn't have a <title> element
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
magentoperformance.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
magentoperformance.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Magentoperformance.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Magentoperformance.de 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.
magentoperformance.de
Open Graph description is not detected on the main page of Magentoperformance. 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: