1.8 sec in total
99 ms
1.4 sec
288 ms
Click here to check amazing Iams content for United States. Otherwise, check out these important facts you probably never knew about iams.com
Find the complete IAMS™ pet food line, learn about our nutritional philosophy and more at Iams.com.
Visit iams.comWe analyzed Iams.com page load time and found that the first response time was 99 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
iams.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value5.6 s
17/100
25%
Value7.6 s
26/100
10%
Value1,220 ms
20/100
30%
Value0.063
97/100
15%
Value15.2 s
7/100
10%
99 ms
371 ms
231 ms
421 ms
23 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 56% of them (43 requests) were addressed to the original Iams.com, 16% (12 requests) were made to and 10% (8 requests) were made to Footer.mars.com. The less responsive or slowest element that took the longest time to load (421 ms) relates to the external source Cloud.typography.com.
Page size can be reduced by 2.4 MB (30%)
8.1 MB
5.7 MB
In fact, the total size of Iams.com main page is 8.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. 60% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 68.6 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 68.6 kB or 79% of the original size.
Potential reduce by 64.6 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. Iams images are well optimized though.
Potential reduce by 611.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 611.4 kB or 66% of the original size.
Potential reduce by 1.7 MB
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. Iams.com needs all CSS files to be minified and compressed as it can save up to 1.7 MB or 73% of the original size.
Number of requests can be reduced by 31 (51%)
61
30
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iams. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
iams.com
99 ms
www.iams.com
371 ms
satelliteLib-ed81b7db8a5151e51a7edc60274dc55d2548d1c6.js
231 ms
fonts.css
421 ms
Telerik.Web.UI.WebResource.axd
23 ms
bootstrap.css
35 ms
global.css
58 ms
WebResource.axd
33 ms
WebResource.axd
42 ms
Telerik.Web.UI.WebResource.axd
59 ms
footer.js.aspx
100 ms
global
130 ms
satellite-55c22cdc66303400170003e9.js
60 ms
BA33D23DC146C04D0.css
60 ms
en-US.png
6 ms
en-CA.png
15 ms
iams_logo83833de96b1f6394958cff030067515e.png
16 ms
buy-now.png
16 ms
vd-homepagehero_mobile.jpg
35 ms
see-a-visible-difference.jpg
67 ms
not_aveg_mob.jpg
37 ms
dog-articles.jpg
67 ms
cat-articles.jpg
36 ms
the-iams-story.jpg
35 ms
subsec-go.jpg
67 ms
lifelong-rewards.jpg
65 ms
subsec-join.jpg
67 ms
ingredients-guide.jpg
68 ms
subsec-learn.jpg
67 ms
the-iams-difference.jpg
80 ms
share-twitter.png
80 ms
share-fb.png
80 ms
youtube.png
80 ms
share-gplus.png
81 ms
footer-go.png
79 ms
gtm.js
101 ms
menu_down_white.png
66 ms
menu-desktop-icon.png
65 ms
mars-icon-font.css
20 ms
footer.css
35 ms
custom.css
48 ms
jquery.1.7.1.noconflict.min.js
54 ms
Dk8FspfgPL0EFO
11 ms
EDVGwKVlcveErP7ZTwL3H2ZEMoW8k92RUf4dgcc8d4b3MG15DyZMs+LztrHSVLEc2Ls6Th6THpYzPb3je4Mnxt1L8Ag07QV4=
12 ms
FaK31mdQTI=
12 ms
Fp+JG6JgXTK5es1HfmyngAePs5IMoW8k92Rkf4tgcccd4bnME15DyUoWvN52VrpKliMaF+fJY9LDUMbnJzxP8OTwWyl+A8vQQU4=
11 ms
AINO0Fe
10 ms
ls0Co3klmj3bOcIHYWUaFmj0Z4wDsu3MEWfY+oYWCCQldnqH+tmTWjl80RxH30bAo76HJaVc2kRh6ms4YcRrDiC0VjvZptaiI3A9Oi4Ni9dEz+5Y2cNCv5RjDr07qZ4ykIPDNNefxn9Iq8QldaacYSXyfmdWKenpjjQcnHVk+qF8vDG7xbvocsSdIZP9PkTOInGeTxI17urahQCfuz+EzcEAXrksXVa77yYzsFPHicHckZ9I3knozqbxEs7rgjvJd5w2soeZIFn7edla6S5cjGRXn8mPSwlPH5Dc8bPD78VorfWZ1BMg==
9 ms
KeTJA14enJCohftRfCTuiGZXIwexyqGbAu7tFxU5ga5W3JKh+DsEh3tuCA9mdjZQspAFr7etU16qcuDip3nyEPI4lfHpEc8jPDk+LMUvlApBOw==
10 ms
10 ms
WXYh8n8p5MkDXh6ckKiF+1F8JO6IZlcjB7HKoZsC7u0XFTmBrlbckqH4OwSHe24ID2Z2NlCykAWvt61TXqpy4OKnefIQ8jiV8ekRzyM8OT4sxS+UCkE7
9 ms
DRPHkIepjI+PeJ5hCeHh6X4BaRdQT8=
9 ms
glyphicons-halflings-regular.woff
43 ms
2Mz697GWZJ4dfTPELAMpE7g==
9 ms
2Mz697GWZJ4dfTPELAMpE7g==
8 ms
analytics.js
164 ms
gateway.min.js
208 ms
iframe_api
132 ms
jquery.sticky.js
82 ms
s-code-contents-d856ec3041c2cff9b1ec16d8dc0e68b09fe2930c.js
91 ms
buy-now-large.png
19 ms
vd-homepagehero_desktop.jpg
83 ms
see-a-visible-difference.jpg
114 ms
not_aveg_desktop.jpg
119 ms
iams-story.jpg
26 ms
lifelong-rewards.jpg
26 ms
ingredients-guide.jpg
88 ms
the-iams-difference.jpg
54 ms
collect
44 ms
cookie-warning.js
10 ms
h1.js
91 ms
custom.js
33 ms
www-widgetapi.js
81 ms
iams-story.jpg
44 ms
foresee_trigger.js
51 ms
s45135340543929
8 ms
6836.js
11 ms
iams.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
iams.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
iams.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iams.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Iams.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.
iams.com
Open Graph data is detected on the main page of Iams. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: