Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

Page Load Speed

4.4 sec in total

First Response

67 ms

Resources Loaded

3.9 sec

Page Rendered

481 ms

About Website

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

Welcome to Equibase.com, your official source for horse racing results, mobile racing data, statistics as well as all other horse racing and thoroughbred racing information. Find everything you need t...

Visit equibase.com

Key Findings

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

Performance Metrics

equibase.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value24.9 s

0/100

10%

TBT (Total Blocking Time)

Value7,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.272

45/100

15%

TTI (Time to Interactive)

Value50.5 s

0/100

10%

Network Requests Diagram

www.equibase.com

67 ms

www.equibase.com

137 ms

inan-giues-thing-starra-your-Thange-Macb-This-br

65 ms

js

218 ms

styles.css

111 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 50% of them (61 requests) were addressed to the original Equibase.com, 13% (16 requests) were made to U713.equibase.com and 8% (10 requests) were made to Cdn-images.bloodhorse.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 426.7 kB (16%)

Content Size

2.7 MB

After Optimization

2.3 MB

In fact, the total size of Equibase.com main page is 2.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. 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 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 348.8 kB

  • Original 384.9 kB
  • After minification 321.7 kB
  • After compression 36.1 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 63.2 kB, which is 16% 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 348.8 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 18.7 kB

  • Original 1.7 MB
  • After minification 1.6 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. Equibase images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 18.9 kB

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

CSS Optimization

-24%

Potential reduce by 40.3 kB

  • Original 167.0 kB
  • After minification 167.0 kB
  • After compression 126.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. Equibase.com needs all CSS files to be minified and compressed as it can save up to 40.3 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (58%)

Requests Now

107

After Optimization

45

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

Accessibility Review

equibase.com accessibility score

67

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

equibase.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

equibase.com SEO score

73

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

High

Image elements do not have [alt] attributes

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Equibase.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), while the claimed language is English. Our system also found out that Equibase.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 Equibase. 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: