9.3 sec in total
472 ms
8.6 sec
168 ms
Welcome to grammer.com homepage info - get ready to check GRAMMER best content for India right away, or after learning these important things about grammer.com
Die GRAMMER AG ist spezialisiert auf die Entwicklung und Herstellung von Komponenten und Systemen für die Pkw-Innenausstattung sowie von Fahrer- und Passagiersitzen für Offroad-Fahrzeuge, Lkw, Busse u...
Visit grammer.comWe analyzed Grammer.com page load time and found that the first response time was 472 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
grammer.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value10.1 s
0/100
25%
Value10.5 s
7/100
10%
Value160 ms
93/100
30%
Value0.002
100/100
15%
Value12.2 s
15/100
10%
472 ms
311 ms
189 ms
381 ms
379 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 86% of them (44 requests) were addressed to the original Grammer.com, 10% (5 requests) were made to Charts25.equitystory.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Grammer.com.
Page size can be reduced by 378.5 kB (15%)
2.5 MB
2.1 MB
In fact, the total size of Grammer.com main page is 2.5 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. 35% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 15.2 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 2.2 kB, which is 11% 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 15.2 kB or 76% of the original size.
Potential reduce by 107.5 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. GRAMMER images are well optimized though.
Potential reduce by 202.4 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 202.4 kB or 69% of the original size.
Potential reduce by 53.3 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. Grammer.com needs all CSS files to be minified and compressed as it can save up to 53.3 kB or 81% of the original size.
Number of requests can be reduced by 27 (55%)
49
22
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GRAMMER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
grammer.com
472 ms
willkommen-bei-grammer.html
311 ms
stylesheet_f19f23cdd4.css
189 ms
Main.css
381 ms
Additional.css
379 ms
grammer.css
373 ms
mootools-core-1.3.2-full-compat-yc.js
573 ms
mootools-more-1.3.2.1-yc.js
571 ms
sdlib.js
616 ms
sdfunc.js
560 ms
Quickie.js
560 ms
mediaboxAdv.js
566 ms
domready.js
744 ms
javascript_bd4d1f63e4.js
743 ms
slim_base.css
379 ms
basemod.css
384 ms
content.css
385 ms
forms.css
433 ms
mediaboxAdv-Dark.css
556 ms
teaser.php
383 ms
logo.gif
203 ms
search.gif
204 ms
arrw_topnav.gif
199 ms
mainnav.png
198 ms
mainnav_li.png
202 ms
subnav.png
201 ms
arrw_subnav.png
386 ms
Banner2012_02_loc.jpg
939 ms
fahnen_logo_web.jpg
3152 ms
emotion_11.jpg
1477 ms
Banner2013_01.jpg
1306 ms
Banner2013_02.jpg
6237 ms
Banner2013_03.jpg
1481 ms
Banner2013_01_Automotive_Seating.jpg
1856 ms
Banner2013_01_seating_bahn.jpg
2599 ms
bussitzauschnitt.jpg
1852 ms
bahn_01.jpg
2796 ms
subc.png
2041 ms
arrw_blue9x8.gif
2045 ms
sidebarnavi.png
2227 ms
arrw_sidebarnav.png
2232 ms
arrw_footer.gif
2407 ms
rss.gif
2412 ms
mobile.png
2593 ms
printer.gif
2597 ms
ga.js
31 ms
__utm.gif
12 ms
teaser.css
195 ms
png_teaser.php
464 ms
teaser_up.gif
192 ms
teaser_link.gif
193 ms
grammer.com 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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
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.
grammer.com 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
grammer.com 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 Grammer.com 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 Grammer.com 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.
grammer.com
Open Graph description is not detected on the main page of GRAMMER. 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: