Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

charliekimball.com

The Official Website of Charlie Kimball

Page Load Speed

9.1 sec in total

First Response

3.2 sec

Resources Loaded

4.9 sec

Page Rendered

907 ms

charliekimball.com screenshot

About Website

Click here to check amazing Charlie Kimball content. Otherwise, check out these important facts you probably never knew about charliekimball.com

The Official Website of Charlie Kimball - IndyCar driver Charlie Kimball featuring news, race reports, schedules, profile and photographs.

Visit charliekimball.com

Key Findings

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

Performance Metrics

charliekimball.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value19.5 s

0/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.538

14/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

charliekimball.com

3220 ms

assets.css

116 ms

stylesheet.css

151 ms

slimbox2.css

168 ms

main.css

154 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 74% of them (70 requests) were addressed to the original Charliekimball.com, 9% (9 requests) were made to Scontent.xx.fbcdn.net and 6% (6 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Charliekimball.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 493.5 kB (9%)

Content Size

5.7 MB

After Optimization

5.2 MB

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

HTML Optimization

-79%

Potential reduce by 62.8 kB

  • Original 79.5 kB
  • After minification 74.1 kB
  • After compression 16.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. 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.8 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 344.8 kB

  • Original 5.5 MB
  • After minification 5.2 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. Charlie Kimball images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 47.1 kB

  • Original 85.6 kB
  • After minification 76.8 kB
  • After compression 38.5 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 47.1 kB or 55% of the original size.

CSS Optimization

-83%

Potential reduce by 38.8 kB

  • Original 46.5 kB
  • After minification 41.7 kB
  • After compression 7.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. Charliekimball.com needs all CSS files to be minified and compressed as it can save up to 38.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (19%)

Requests Now

89

After Optimization

72

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

Accessibility Review

charliekimball.com accessibility score

79

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-hidden="true"] elements contain focusable descendents

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

charliekimball.com best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

charliekimball.com SEO score

58

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Charliekimball.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Charliekimball.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 Charlie Kimball. 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: