2.4 sec in total
310 ms
1.9 sec
178 ms
Click here to check amazing Igmco content. Otherwise, check out these important facts you probably never knew about igmco.de
Wir produzieren Komponeneten aus Sphäroguss GGG60, GGG70 ,GGG80 für unsere Kunden aus Automobielindustrie (LKW/PKW).
Visit igmco.deWe analyzed Igmco.de page load time and found that the first response time was 310 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
igmco.de performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value5.8 s
15/100
25%
Value5.7 s
51/100
10%
Value120 ms
97/100
30%
Value0.731
6/100
15%
Value6.2 s
62/100
10%
310 ms
333 ms
217 ms
64 ms
217 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Igmco.de, 30% (6 requests) were made to U.jimdo.com and 30% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (843 ms) relates to the external source U.jimdo.com.
Page size can be reduced by 522.2 kB (57%)
912.5 kB
390.3 kB
In fact, the total size of Igmco.de main page is 912.5 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. 30% of websites need less resources to load. Javascripts take 564.4 kB which makes up the majority of the site volume.
Potential reduce by 20.9 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 20.9 kB or 58% of the original size.
Potential reduce by 3.8 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. Igmco images are well optimized though.
Potential reduce by 348.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 348.4 kB or 62% of the original size.
Potential reduce by 149.1 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. Igmco.de needs all CSS files to be minified and compressed as it can save up to 149.1 kB or 75% of the original size.
Number of requests can be reduced by 6 (33%)
18
12
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Igmco. 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 from 4 to 1 for CSS and as a result speed up the page load time.
igmco.de
310 ms
www.cast-iron-parts.com
333 ms
main.css
217 ms
layout.css
64 ms
font.css
217 ms
web.js.81df69f80213857d0c7a.js
124 ms
image.jpg
233 ms
ga.js
157 ms
analytics.js
156 ms
content_bg.gif
135 ms
header.jpg
843 ms
unten_bg.gif
134 ms
web_oldtemplate.css.2d44259dc7097634303898168c3a0804.css
140 ms
image.jpg
225 ms
image.jpg
250 ms
__utm.gif
34 ms
__utm.gif
29 ms
collect
14 ms
collect
8 ms
loginstate
226 ms
igmco.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
Image elements do not have [alt] attributes
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.
igmco.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
igmco.de 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igmco.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 Igmco.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.
igmco.de
Open Graph description is not detected on the main page of Igmco. 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: