6.5 sec in total
373 ms
5.8 sec
353 ms
Visit matthias-glaessner.de now to see the best up-to-date Matthias Glaessner content and also check out these interesting facts you probably never knew about matthias-glaessner.de
Beratung und Entwicklung, TYPO3 Updates, TYPO3 SEO, Barrierearmut nach BiTV 2.0, TYPO3 Solr Suche, Extension-Entwicklung und vieles mehr. Maßgeschneiderte Profi-Lösungen seit 2007.
Visit matthias-glaessner.deWe analyzed Matthias-glaessner.de page load time and found that the first response time was 373 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
matthias-glaessner.de performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value4.3 s
42/100
25%
Value7.9 s
23/100
10%
Value190 ms
90/100
30%
Value0
100/100
15%
Value7.3 s
50/100
10%
373 ms
384 ms
736 ms
186 ms
282 ms
Our browser made a total of 24 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Matthias-glaessner.de, 71% (17 requests) were made to Typo3-senior-entwickler.de and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Exali.de.
Page size can be reduced by 355.2 kB (32%)
1.1 MB
764.1 kB
In fact, the total size of Matthias-glaessner.de main page is 1.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 981.5 kB which makes up the majority of the site volume.
Potential reduce by 37.1 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 37.1 kB or 75% of the original size.
Potential reduce by 315.2 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, Matthias Glaessner needs image optimization as it can save up to 315.2 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.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 0 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. Matthias-glaessner.de has all CSS files already compressed.
Number of requests can be reduced by 3 (25%)
12
9
The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Matthias Glaessner. 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.
matthias-glaessner.de
373 ms
matthias-glaessner.de
384 ms
typo3-senior-entwickler.de
736 ms
merged-9802161ef56e9c1dfecf890bcc1663fc-min.css.gzip
186 ms
logo.png
282 ms
banner.js
51 ms
merged-e12133b192c6e04d6b3b2254f76294d3.js
700 ms
analytics.js
19 ms
spinner.gif
98 ms
bonn.jpg
443 ms
collect
13 ms
icomoon.woff
240 ms
fontawesome-webfont.woff
477 ms
js
56 ms
Haftpflicht_Siegel_0_e871412ed650577a4f9308b2ad379714.png
3591 ms
csm_extension-entwicklung-greyscale-compressor_937a066337.jpg
100 ms
csm_template-erstellung_4604be4e5b.jpg
102 ms
fce-compressor.jpg
100 ms
csm_wartung_c299f413e8.jpg
104 ms
csm_performance_248a86ee79.jpg
103 ms
csm_seo_df01f4af3f.jpg
102 ms
referenzen.png
288 ms
csm_faq-greyscale-compressor_e3412c66b2.jpg
196 ms
gvb_logo.svg
195 ms
matthias-glaessner.de accessibility score
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
matthias-glaessner.de 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
matthias-glaessner.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Matthias-glaessner.de 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 Matthias-glaessner.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.
matthias-glaessner.de
Open Graph description is not detected on the main page of Matthias Glaessner. 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: