Tools & Wizards About Us
indylights.com screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

indylights.com

The Official Site of the INDY NXT, Drivers, Schedule & Shop | IndyCar.com

Page Load Speed

2.7 sec in total

First Response

15 ms

Resources Loaded

1.2 sec

Page Rendered

1.4 sec

indylights.com screenshot

About Website

Welcome to indylights.com homepage info - get ready to check INDY Lights best content for United States right away, or after learning these important things about indylights.com

The official site of INDY NXT by Firestone, the developmental series of INDYCAR. Get the latest news, schedule, driver profiles, championship standings, race results and more.

Visit indylights.com

Key Findings

We analyzed Indylights.com page load time and found that the first response time was 15 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

indylights.com performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value2,240 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.386

27/100

15%

TTI (Time to Interactive)

Value24.4 s

0/100

10%

Network Requests Diagram

indylights.com

15 ms

indylights

101 ms

indynxt

110 ms

desktop.css

65 ms

responsive.css

52 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Indylights.com, 39% (33 requests) were made to Digbza2f4g9qo.cloudfront.net and 18% (15 requests) were made to Indycar.com. The less responsive or slowest element that took the longest time to load (442 ms) relates to the external source Analytics.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 883.4 kB (18%)

Content Size

4.8 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indylights.com main page is 4.8 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. 70% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 88.8 kB

  • Original 113.6 kB
  • After minification 75.0 kB
  • After compression 24.7 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 38.6 kB, which is 34% 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 88.8 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 32.1 kB

  • Original 3.4 MB
  • After minification 3.4 MB

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 Lights images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 501.9 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 522.1 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 501.9 kB or 49% of the original size.

CSS Optimization

-90%

Potential reduce by 260.6 kB

  • Original 290.1 kB
  • After minification 181.9 kB
  • After compression 29.5 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. Indylights.com needs all CSS files to be minified and compressed as it can save up to 260.6 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (51%)

Requests Now

75

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indylights.com

indylights.com

15 ms

indylights

indylights

101 ms

indynxt

indynxt

110 ms

desktop.css

desktop.css

65 ms

responsive.css

responsive.css

52 ms

theme-desktop.css

theme-desktop.css

51 ms

theme-responsive.css

theme-responsive.css

54 ms

sprite-updated.svg

sprite-updated.svg

65 ms

INDY-NXT-Dark

INDY-NXT-Dark

40 ms

otSDKStub.js

otSDKStub.js

61 ms

widget.js

widget.js

422 ms

require.min.js

require.min.js

61 ms

desktop.js

desktop.js

36 ms

gpt.js

gpt.js

130 ms

08-25-Abel-Wins-POR-Primary.jpg

08-25-Abel-Wins-POR-Primary.jpg

68 ms

Milwaukee.jpg

Milwaukee.jpg

50 ms

Universal-Drivers.jpg

Universal-Drivers.jpg

65 ms

Universal-News.jpg

Universal-News.jpg

78 ms

Milwaukee.jpg

Milwaukee.jpg

66 ms

TheMilwaukeeMile.png

TheMilwaukeeMile.png

49 ms

PeacockStreaming.png

PeacockStreaming.png

65 ms

INDYCAR-LIVE-IL.png

INDYCAR-LIVE-IL.png

65 ms

SiriusXM2024.png

SiriusXM2024.png

68 ms

TagHeuer.png

TagHeuer.png

68 ms

Nashville-Superspeedway.jpg

Nashville-Superspeedway.jpg

75 ms

NashvilleSuperspeedway.png

NashvilleSuperspeedway.png

74 ms

LouisFoster.jpg

LouisFoster.jpg

76 ms

26-INXT-Orange-T.png

26-INXT-Orange-T.png

75 ms

JacobAbel.jpg

JacobAbel.jpg

76 ms

51-INXT-Red-T.png

51-INXT-Red-T.png

80 ms

CaioCollet.jpg

CaioCollet.jpg

80 ms

18-INXT-Green-T.png

18-INXT-Green-T.png

79 ms

08-25-Abel-Portland-IC.jpg

08-25-Abel-Portland-IC.jpg

79 ms

08-24-Foster-Pole.jpg

08-24-Foster-Pole.jpg

79 ms

08-24-Foster-Action.jpg

08-24-Foster-Action.jpg

80 ms

08-23-Foster.jpg

08-23-Foster.jpg

85 ms

firestone-logo.png

firestone-logo.png

82 ms

08-25-NXT-Race-Highlights-Portland.jpg

08-25-NXT-Race-Highlights-Portland.jpg

84 ms

08-25-NXT-Race-Interviews-Portland.jpg

08-25-NXT-Race-Interviews-Portland.jpg

82 ms

08-24-NXT-Quals-Highlights-Portland.jpg

08-24-NXT-Quals-Highlights-Portland.jpg

82 ms

08-23-NXT-Practice1-Portland.jpg

08-23-NXT-Practice1-Portland.jpg

83 ms

css

css

50 ms

aif5psz.css

aif5psz.css

44 ms

font-awesome.min.css

font-awesome.min.css

33 ms

p.css

p.css

25 ms

f277e317-ab9e-4f9f-b323-7f256ab3860a.json

f277e317-ab9e-4f9f-b323-7f256ab3860a.json

44 ms

gtm.js

gtm.js

295 ms

gpt.js

gpt.js

294 ms

fbevents.js

fbevents.js

67 ms

uwt.js

uwt.js

59 ms

pubads_impl.js

pubads_impl.js

34 ms

init.js

init.js

33 ms

header.js

header.js

257 ms

carousel.js

carousel.js

344 ms

countdown.js

countdown.js

417 ms

tabs.js

tabs.js

419 ms

tab-slider.js

tab-slider.js

417 ms

location

location

253 ms

jquery.min.js

jquery.min.js

245 ms

util.js

util.js

269 ms

modernizr.min.js

modernizr.min.js

195 ms

fastclick.min.js

fastclick.min.js

194 ms

svg4everybody.min.js

svg4everybody.min.js

395 ms

otBannerSdk.js

otBannerSdk.js

186 ms

ads

ads

136 ms

container.html

container.html

249 ms

d

d

111 ms

d

d

133 ms

d

d

190 ms

d

d

134 ms

d

d

190 ms

widget_app_base_1724056634836.js

widget_app_base_1724056634836.js

79 ms

0d551c6f47.js

0d551c6f47.js

221 ms

adsct

adsct

325 ms

adsct

adsct

442 ms

jquery.mobile.events.js

jquery.mobile.events.js

140 ms

slick.min.js

slick.min.js

135 ms

jquery.countdown.min.js

jquery.countdown.min.js

128 ms

on.screen.min.js

on.screen.min.js

96 ms

3247541205140785424

3247541205140785424

111 ms

abg_lite.js

abg_lite.js

118 ms

window_focus.js

window_focus.js

223 ms

ufs_web_display.js

ufs_web_display.js

122 ms

icon.png

icon.png

107 ms

Accessibility Review

indylights.com accessibility score

86

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[role] values are not valid

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.

Best Practices

indylights.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

indylights.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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 Indylights.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 Indylights.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

indylights.com

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