4.9 sec in total
114 ms
3.4 sec
1.4 sec
Visit ill.i.am now to see the best up-to-date Ill I content for United States and also check out these interesting facts you probably never knew about ill.i.am
Visit ill.i.amWe analyzed Ill.i.am page load time and found that the first response time was 114 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ill.i.am performance score
114 ms
603 ms
68 ms
63 ms
461 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 88% of them (85 requests) were addressed to the original Ill.i.am, 5% (5 requests) were made to F.vimeocdn.com and 3% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ill.i.am.
Page size can be reduced by 2.3 MB (27%)
8.5 MB
6.2 MB
In fact, the total size of Ill.i.am main page is 8.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. 45% of websites need less resources to load. Images take 6.8 MB which makes up the majority of the site volume.
Potential reduce by 75.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. This page needs HTML code to be minified as it can gain 24.2 kB, which is 28% 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 75.9 kB or 87% of the original size.
Potential reduce by 967.0 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, Ill I needs image optimization as it can save up to 967.0 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.0 MB
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 1.0 MB or 76% of the original size.
Potential reduce by 218.6 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. Ill.i.am needs all CSS files to be minified and compressed as it can save up to 218.6 kB or 86% of the original size.
Number of requests can be reduced by 10 (11%)
95
85
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ill I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ill.i.am
114 ms
ill.i.am
603 ms
css
68 ms
froogaloop2.min.js
63 ms
combined.v1447356463.js
461 ms
combined.v1446509777.css
245 ms
style.css
79 ms
handlebars.min.js
142 ms
js
41 ms
jquery.storelocator.js
177 ms
logo-white-sm.png
216 ms
logo-white.png
216 ms
logo-black.png
218 ms
nav_up.png
233 ms
563284af-17b0-4682-9737-122432398419
624 ms
5632854e-abf0-44fe-960d-122432398419
586 ms
56328581-83bc-431b-a7f0-1edc32398419
674 ms
563285ae-da98-41e0-ac6a-1f4b32398419
639 ms
563285c4-211c-448d-98c2-122432398419
670 ms
bg_about.jpg
539 ms
5632a547-17a0-410d-8827-464c32398419
777 ms
5632a5bc-5638-4837-aa4c-464c32398419
851 ms
5632a5f3-6068-49cd-8a6b-464632398419
887 ms
5632a61f-dd78-44de-8378-5da232398419
880 ms
5632a644-8d98-4be7-9a86-43ce32398419
923 ms
5632a70a-78d4-4cbe-9f60-464632398419
912 ms
5632a7ac-86f0-45fa-b3c3-43ce32398419
1014 ms
5632a8bc-7bd0-4a37-bb79-464632398419
1087 ms
5632a9e2-c7a4-4fb8-926f-69ed32398419
1132 ms
5632e80a-8880-4f02-a1aa-0f4732398419
961 ms
5632e80a-42c0-4d21-aee8-0f4a32398419
980 ms
5632e85c-d0e4-458c-bccd-5da232398419
994 ms
5632e85b-da48-46e3-b147-69ed32398419
1032 ms
5632e8de-f578-4445-bd62-69ed32398419
1052 ms
5632e8dd-f720-4578-88ea-5da232398419
1061 ms
5632eaa1-d620-4d44-b0be-0cc732398419
1081 ms
5632eaa1-84f8-4472-aa53-7afb32398419
1098 ms
5633befe-b798-4edc-b2b5-4d5c32398419
1118 ms
5633befe-3ac4-4e8e-943a-6bb832398419
1127 ms
5633b245-d870-407a-afd3-4fcd32398419
1157 ms
5633b245-f0bc-4d77-a6e5-4fa132398419
1157 ms
5632e9b0-8a54-49c4-a6a8-5da232398419
1164 ms
5632e9af-f108-4d40-aef9-69ed32398419
1197 ms
5632eb9e-4ea8-4ff9-8199-7d3132398419
1194 ms
5632eb9e-4c68-4fdf-9210-7afb32398419
1198 ms
ga.js
123 ms
5632e9f5-ff90-4906-ba7c-5da232398419
1168 ms
144217778
89 ms
player.js
110 ms
player.css
95 ms
vuid.min.js
63 ms
__utm.gif
43 ms
__utm.gif
33 ms
infowindow-description.html
1019 ms
location-list-description.html
1027 ms
5632e9f5-8168-4a46-a5e7-360d32398419
1059 ms
56328b30-ce6c-474c-a556-1edc32398419
1213 ms
proxy.html
55 ms
542264517.jpg
144 ms
56328bd3-e854-4bd0-9ac8-1a3932398419
906 ms
56328b6a-1ec0-4be4-a980-154832398419
893 ms
56328b89-d9fc-4f63-87a1-1edc32398419
851 ms
56328bf9-7448-44f7-9463-1a7032398419
842 ms
56328ba8-66cc-4054-a8b6-7a0532398419
838 ms
56328b04-767c-4797-b007-683432398419
1009 ms
56328c0b-957c-4528-aa13-7a0532398419
922 ms
56328ac1-50c0-4294-930a-122432398419
861 ms
5632ae75-890c-4a5a-8aed-741b32398419
668 ms
5632ae75-3c68-411c-b968-748a32398419
659 ms
5632b2b4-9db0-4536-841a-741b32398419
666 ms
5632b2b4-52bc-44d9-bb5a-748a32398419
691 ms
5632b1ae-87bc-4623-bb50-7c2f32398419
655 ms
5632b1ad-da48-49ab-b46f-69ed32398419
664 ms
5632b227-6ca4-412c-9a63-017e32398419
686 ms
5632b227-d808-4745-9e3c-69ed32398419
671 ms
5632b303-db04-447a-beee-69ed32398419
682 ms
5632b303-40c0-4f4c-9a73-017e32398419
693 ms
5632ad7d-f464-4424-ac58-678d32398419
688 ms
5632ad7d-8e14-4679-aa94-6f4232398419
672 ms
5632accc-cc40-4ae7-971d-69ed32398419
679 ms
5632accc-6cf8-4a85-bc7b-746932398419
678 ms
5632ad49-0aa4-4c63-a4e0-678d32398419
661 ms
5632ad48-f4a4-4cf6-a0c2-6d0432398419
682 ms
5632ac18-bba0-4ec9-9a26-5da232398419
694 ms
5632ac18-c354-409a-af2c-43ce32398419
666 ms
5638bdab-8b64-45a1-973f-14ec32398419
882 ms
5638b841-8ea4-4dfb-af3d-027632398419
916 ms
5625eb26-6ccc-4c24-b3d2-470532398419
753 ms
540e386e-beb8-499c-83f5-6ac1ae8f380d
777 ms
550b343c-8e70-4ee1-b460-27de323984d2
837 ms
540e356b-94a8-4592-959d-65eeae8f380d
734 ms
icon_facebook.png
790 ms
icon_twitter.png
781 ms
icon_instagram.png
646 ms
ajax-loader.gif
665 ms
left_arrow.png
640 ms
right_arrow.png
652 ms
ill.i.am SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ill.i.am can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ill.i.am 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.
ill.i.am
Open Graph description is not detected on the main page of Ill I. 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: