Tools & Wizards About Us
igniteband.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

igniteband.com

IGNITE

Page Load Speed

2.5 sec in total

First Response

203 ms

Resources Loaded

1.5 sec

Page Rendered

870 ms

igniteband.com screenshot

About Website

Click here to check amazing IGNITE Band content. Otherwise, check out these important facts you probably never knew about igniteband.com

The official IGNITE website. Orange County Hardcore since 1993.

Visit igniteband.com

Key Findings

We analyzed Igniteband.com page load time and found that the first response time was 203 ms and then it took 2.3 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.

Performance Metrics

igniteband.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value2,830 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

igniteband.com

203 ms

pre_tumblelog.js

71 ms

index.build.css

75 ms

normalize.min.css

77 ms

style.min.css

80 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Igniteband.com, 20% (14 requests) were made to 64.media.tumblr.com and 17% (12 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (926 ms) relates to the external source A0.awsstatic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.8 kB (12%)

Content Size

973.8 kB

After Optimization

854.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Igniteband.com main page is 973.8 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. Only a small number of websites need less resources to load. Images take 460.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 112.2 kB

  • Original 135.1 kB
  • After minification 119.7 kB
  • After compression 22.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 15.4 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 112.2 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 4.3 kB

  • Original 460.7 kB
  • After minification 456.4 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. IGNITE Band images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 275.8 kB
  • After minification 275.8 kB
  • After compression 273.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 428 B

  • Original 102.1 kB
  • After minification 102.1 kB
  • After compression 101.7 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. Igniteband.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (41%)

Requests Now

59

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IGNITE Band. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

igniteband.com

igniteband.com

203 ms

pre_tumblelog.js

pre_tumblelog.js

71 ms

index.build.css

index.build.css

75 ms

normalize.min.css

normalize.min.css

77 ms

style.min.css

style.min.css

80 ms

css

css

47 ms

css

css

70 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

77 ms

bilmur.min.js

bilmur.min.js

72 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

76 ms

stylesheet.css

stylesheet.css

76 ms

jquery.min.js

jquery.min.js

115 ms

all.min.js

all.min.js

115 ms

index.build.js

index.build.js

115 ms

awshome_s_code.js

awshome_s_code.js

926 ms

sdk.js

sdk.js

198 ms

gF17466ZO3U

gF17466ZO3U

149 ms

like_iframe.html

like_iframe.html

163 ms

H3MFpyEMVjQ

H3MFpyEMVjQ

149 ms

tumblr_ptkrr1eXSl1r7vto3o1_1280.jpg

tumblr_ptkrr1eXSl1r7vto3o1_1280.jpg

295 ms

tumblr_ptkrr1eXSl1r7vto3o1_500.jpg

tumblr_ptkrr1eXSl1r7vto3o1_500.jpg

265 ms

tumblr_pshisqU5a61r7vto3o1_1280.jpg

tumblr_pshisqU5a61r7vto3o1_1280.jpg

295 ms

tumblr_pshisqU5a61r7vto3o1_500.jpg

tumblr_pshisqU5a61r7vto3o1_500.jpg

266 ms

tumblr_po2bdwfw3Z1r7vto3o1_1280.jpg

tumblr_po2bdwfw3Z1r7vto3o1_1280.jpg

294 ms

tumblr_po2bdwfw3Z1r7vto3o1_500.jpg

tumblr_po2bdwfw3Z1r7vto3o1_500.jpg

279 ms

tumblr_pi9d25JnoI1r7vto3o1_1280.jpg

tumblr_pi9d25JnoI1r7vto3o1_1280.jpg

300 ms

tumblr_pi9d25JnoI1r7vto3o1_500.jpg

tumblr_pi9d25JnoI1r7vto3o1_500.jpg

289 ms

tumblr_pfkif9CJic1r7vto3o1_1280.jpg

tumblr_pfkif9CJic1r7vto3o1_1280.jpg

294 ms

tumblr_pfkif9CJic1r7vto3o1_500.jpg

tumblr_pfkif9CJic1r7vto3o1_500.jpg

290 ms

tumblr_p7r5fwF9KX1r7vto3o1_1280.jpg

tumblr_p7r5fwF9KX1r7vto3o1_1280.jpg

296 ms

tumblr_p7r5fwF9KX1r7vto3o1_500.jpg

tumblr_p7r5fwF9KX1r7vto3o1_500.jpg

298 ms

tumblr_p6f3dcovev1r7vto3o1_1280.jpg

tumblr_p6f3dcovev1r7vto3o1_1280.jpg

321 ms

tumblr_p6f3dcovev1r7vto3o1_500.jpg

tumblr_p6f3dcovev1r7vto3o1_500.jpg

320 ms

tumblr_static_1r2nr845lo9w0oc0g48wkgk48.jpg

tumblr_static_1r2nr845lo9w0oc0g48wkgk48.jpg

288 ms

ajax-loader.gif

ajax-loader.gif

183 ms

160 ms

ga.js

ga.js

242 ms

impixu

impixu

240 ms

g.gif

g.gif

160 ms

impixu

impixu

146 ms

gF17466ZO3U

gF17466ZO3U

150 ms

H3MFpyEMVjQ

H3MFpyEMVjQ

437 ms

analytics.html

analytics.html

33 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

52 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

71 ms

4A0JgFjIAAA==

4A0JgFjIAAA==

8 ms

login_check.html

login_check.html

31 ms

social-sprite.png

social-sprite.png

31 ms

share-icons.png

share-icons.png

21 ms

ajax-loader.gif

ajax-loader.gif

22 ms

sdk.js

sdk.js

41 ms

consent

consent

128 ms

__utm.gif

__utm.gif

22 ms

www-player.css

www-player.css

19 ms

www-embed-player.js

www-embed-player.js

37 ms

base.js

base.js

62 ms

cs.js

cs.js

9 ms

header.build.js

header.build.js

183 ms

exceptions.js

exceptions.js

184 ms

index.build.js

index.build.js

187 ms

ad_status.js

ad_status.js

319 ms

cdn.json

cdn.json

252 ms

g.gif

g.gif

234 ms

vD-PFjxSijoP4-I0oY5JcElr_81RPxK9SqvIhUi9qS8.js

vD-PFjxSijoP4-I0oY5JcElr_81RPxK9SqvIhUi9qS8.js

190 ms

embed.js

embed.js

106 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

67 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

68 ms

Create

Create

98 ms

id

id

87 ms

Accessibility Review

igniteband.com accessibility score

76

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

igniteband.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

igniteband.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igniteband.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 Igniteband.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.

Social Sharing Optimization

igniteband.com

Open Graph data is detected on the main page of IGNITE Band. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: