Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

indymini.com

IU Health 500 Festival Mini-Marathon

Page Load Speed

3.8 sec in total

First Response

210 ms

Resources Loaded

3.5 sec

Page Rendered

166 ms

indymini.com screenshot

About Website

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

The IU Health 500 Festival Mini-Marathon is one of the nation's most iconic half marathons. The race starts and finishes in Downtown Indianapolis and includes a lap around the Indianapolis Motor S...

Visit indymini.com

Key Findings

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

Performance Metrics

indymini.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value33.8 s

0/100

25%

SI (Speed Index)

Value26.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,480 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.523

15/100

15%

TTI (Time to Interactive)

Value51.0 s

0/100

10%

Network Requests Diagram

www.indymini.com

210 ms

www.indymini.com

515 ms

fbevents.js

33 ms

bf142ab97713e117b04527c.js

83 ms

gtm.js

97 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 62% of them (41 requests) were addressed to the original Indymini.com, 27% (18 requests) were made to Cdn.saffire.com and 5% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Indymini.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 655.3 kB (50%)

Content Size

1.3 MB

After Optimization

651.6 kB

In fact, the total size of Indymini.com main page is 1.3 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. 55% of websites need less resources to load. Javascripts take 884.8 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 62.2 kB

  • Original 94.4 kB
  • After minification 91.0 kB
  • After compression 32.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 62.2 kB or 66% of the original size.

Image Optimization

-3%

Potential reduce by 4.0 kB

  • Original 132.7 kB
  • After minification 128.7 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 Mini images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 481.8 kB

  • Original 884.8 kB
  • After minification 788.5 kB
  • After compression 403.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 481.8 kB or 54% of the original size.

CSS Optimization

-55%

Potential reduce by 107.2 kB

  • Original 195.0 kB
  • After minification 184.5 kB
  • After compression 87.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. Indymini.com needs all CSS files to be minified and compressed as it can save up to 107.2 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (70%)

Requests Now

61

After Optimization

18

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

Accessibility Review

indymini.com accessibility score

88

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

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

Links do not have a discernible name

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

indymini.com SEO score

79

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Open Graph description is not detected on the main page of Indy Mini. 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: