5.8 sec in total
1.8 sec
3.3 sec
599 ms
Visit indyplanet.us now to see the best up-to-date Indy Planet content for United States and also check out these interesting facts you probably never knew about indyplanet.us
Visit indyplanet.usWe analyzed Indyplanet.us page load time and found that the first response time was 1.8 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
indyplanet.us performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value8.7 s
1/100
25%
Value6.0 s
47/100
10%
Value310 ms
78/100
30%
Value0
100/100
15%
Value9.0 s
34/100
10%
1843 ms
18 ms
18 ms
20 ms
18 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 44% of them (41 requests) were addressed to the original Indyplanet.us, 37% (34 requests) were made to Comics.indyplanet.com and 16% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Indyplanet.us.
Page size can be reduced by 873.3 kB (25%)
3.5 MB
2.6 MB
In fact, the total size of Indyplanet.us main page is 3.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 65.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. 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 65.2 kB or 85% of the original size.
Potential reduce by 65.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. Indy Planet images are well optimized though.
Potential reduce by 291.6 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 291.6 kB or 76% of the original size.
Potential reduce by 451.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. Indyplanet.us needs all CSS files to be minified and compressed as it can save up to 451.3 kB or 88% of the original size.
Number of requests can be reduced by 37 (49%)
76
39
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indy Planet. 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 19 to 1 for CSS and as a result speed up the page load time.
1843 ms
wp-emoji-release.min.js
18 ms
dp-template-editor.css
18 ms
mgwoocommercebrands.css
20 ms
smart-coupon.css
18 ms
magnific.css
21 ms
magnific-custom.css
21 ms
woocommerce-wishlists.css
25 ms
woocommerce-layout.css
32 ms
woocommerce.css
27 ms
style.css
25 ms
css
73 ms
css
74 ms
css
74 ms
style.css
32 ms
shortcodes.css
32 ms
shortcodes_responsive.css
35 ms
jquery.js
38 ms
jquery-migrate.min.js
36 ms
magnific.js
36 ms
magnific-custom.js
36 ms
woocommerce-wishlists.js
35 ms
bootstrap-modal.js
36 ms
style.css
40 ms
frontend-builder-global-functions.js
41 ms
add-to-cart.min.js
40 ms
jquery.blockUI.min.js
40 ms
woocommerce.min.js
39 ms
jquery.cookie.min.js
43 ms
cart-fragments.min.js
41 ms
woocommerce-pip-client.js
40 ms
custom.js
42 ms
jquery.fitvids.js
42 ms
waypoints.min.js
41 ms
jquery.magnific-popup.js
42 ms
frontend-builder-scripts.js
42 ms
wp-embed.min.js
42 ms
main-styles.css
42 ms
frontend-builder-style.css
30 ms
woocommerce-smallscreen.css
234 ms
grayspiral1.png
264 ms
394 ms
IP_star_flare.jpg
50 ms
ip_logo_2015_500X.png
43 ms
Z.png
84 ms
20463_134389B-200x300.jpg
50 ms
17474_134385B-200x300.jpg
50 ms
17474_135154B-200x300.jpg
48 ms
20544_135417B-200x300.jpg
49 ms
19254_133388B-200x300.jpg
80 ms
3374_133869B-200x300.jpg
81 ms
17487_117530B-200x300.jpg
78 ms
15774_135592B-200x300.jpg
79 ms
19963_131205B-200x300.jpg
86 ms
1629_135439B-200x300.jpg
83 ms
20627_135852B-200x300.jpg
82 ms
20627_135851B-200x300.jpg
83 ms
20627_135850B-200x300.jpg
83 ms
20190_132621B-200x300.jpg
84 ms
20327_133564B-200x300.jpg
85 ms
8292_133490B-200x300.jpg
87 ms
5627_62434B-200x300.jpg
84 ms
5627_70487B-200x300.jpg
85 ms
14271_134402B-200x300.jpg
87 ms
1831_134508B-200x300.jpg
86 ms
7475_134396B-200x300.jpg
87 ms
20472_134519B-200x300.jpg
87 ms
20112_134988B-200x300.jpg
89 ms
20598_135308B-200x300.jpg
87 ms
9354_65167b-200x300.jpg
88 ms
3571_82263b-200x300.jpg
488 ms
3965_128632b-200x300.jpg
596 ms
10623_91846b-200x300.jpg
452 ms
2449_127858B-200x300.jpg
456 ms
2449_127862B-200x300.jpg
468 ms
sluggy15.jpg
103 ms
KB_728x90.png
105 ms
u-WUoqrET9fUeobQW7jkRSZ2oysoEQEeKwjgmXLRnTc.ttf
32 ms
DXI1ORHCpsQm3Vp6mXoaTY3LH2FgLjViKkqswU-xtII.ttf
32 ms
MTP_ySUJH_bn48VBG8sNSo3LH2FgLjViKkqswU-xtII.ttf
63 ms
k3k702ZOKiLJc3WVjuplzI3LH2FgLjViKkqswU-xtII.ttf
32 ms
EInbV5DfGHOiMmvb1Xr-ho3LH2FgLjViKkqswU-xtII.ttf
32 ms
JdU2LguLZettxbfEVhxaCQLUuEpTyoUstqEm5AMlJo4.ttf
63 ms
dOHPuLxZLrMk445slyoc7PesZW2xOQ-xsNqO47m55DA.ttf
60 ms
IU2I5IZfkiURW7PugFx42ALUuEpTyoUstqEm5AMlJo4.ttf
58 ms
VdagwMxBFZkgd4HennBoVgLUuEpTyoUstqEm5AMlJo4.ttf
61 ms
ETmodules_v2_4.ttf
65 ms
IhuqmeHx65TaW6CiR2l0VALUuEpTyoUstqEm5AMlJo4.ttf
59 ms
My-1w7AxI_mgSEanxCPGDQLUuEpTyoUstqEm5AMlJo4.ttf
59 ms
mRDHwJdvwTinms3TRtD3HQLUuEpTyoUstqEm5AMlJo4.ttf
62 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
59 ms
JcQUq3K39RZrUxrrs7pjpwLUuEpTyoUstqEm5AMlJo4.ttf
61 ms
WH1LIXt_3tFIWh2VS_oVD-vvDin1pK8aKteLpeZ5c0A.ttf
62 ms
indyplanet.us 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-*] attributes do not match their roles
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
indyplanet.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
indyplanet.us 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indyplanet.us 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 Indyplanet.us 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.
indyplanet.us
Open Graph description is not detected on the main page of Indy Planet. 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: