Tools & Wizards About Us
ridinghorses.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

ridinghorses.com

HOME | Fences Over Bee Cave

Page Load Speed

1.8 sec in total

First Response

77 ms

Resources Loaded

1.6 sec

Page Rendered

63 ms

ridinghorses.com screenshot

About Website

Welcome to ridinghorses.com homepage info - get ready to check Ridinghorses best content right away, or after learning these important things about ridinghorses.com

Visit ridinghorses.com

Key Findings

We analyzed Ridinghorses.com page load time and found that the first response time was 77 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

ridinghorses.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

www.ridinghorses.com

77 ms

minified.js

37 ms

focus-within-polyfill.js

33 ms

polyfill.min.js

996 ms

thunderbolt-commons.09398ec1.bundle.min.js

67 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ridinghorses.com, 44% (18 requests) were made to Static.parastorage.com and 29% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (996 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 977.7 kB (53%)

Content Size

1.8 MB

After Optimization

857.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ridinghorses.com main page is 1.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. 50% of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 795.3 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 206.8 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 795.3 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 391.2 kB
  • After minification 391.2 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. Ridinghorses images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 182.3 kB

  • Original 441.4 kB
  • After minification 441.4 kB
  • After compression 259.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 182.3 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (45%)

Requests Now

22

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ridinghorses.com

www.ridinghorses.com

77 ms

minified.js

minified.js

37 ms

focus-within-polyfill.js

focus-within-polyfill.js

33 ms

polyfill.min.js

polyfill.min.js

996 ms

thunderbolt-commons.09398ec1.bundle.min.js

thunderbolt-commons.09398ec1.bundle.min.js

67 ms

main.e5a43201.bundle.min.js

main.e5a43201.bundle.min.js

70 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

16 ms

lodash.min.js

lodash.min.js

68 ms

react.production.min.js

react.production.min.js

67 ms

react-dom.production.min.js

react-dom.production.min.js

70 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

69 ms

BCRC%20Horizontal%20Logo%20with%20Green.jpg

BCRC%20Horizontal%20Logo%20with%20Green.jpg

199 ms

b3134a_e24f58b15dc04696b3f36858600b2d45~mv2.jpg

b3134a_e24f58b15dc04696b3f36858600b2d45~mv2.jpg

370 ms

b3134a_d699d27cf10b4216bc9936e3ea211daf~mv2.jpg

b3134a_d699d27cf10b4216bc9936e3ea211daf~mv2.jpg

394 ms

b3134a_38afab139c1c457d8b27e3aefdb036dd~mv2.jpg

b3134a_38afab139c1c457d8b27e3aefdb036dd~mv2.jpg

301 ms

file.jpeg%203x

file.jpeg%203x

404 ms

BCRC%20Parking%20Info%202-min.jpg

BCRC%20Parking%20Info%202-min.jpg

283 ms

file.jpeg

file.jpeg

363 ms

bundle.min.js

bundle.min.js

88 ms

83ae2051-dcdd-4931-9946-8be747a40d00.woff

83ae2051-dcdd-4931-9946-8be747a40d00.woff

22 ms

764779cf-076d-427a-87b4-136ccc83fba0.woff

764779cf-076d-427a-87b4-136ccc83fba0.woff

23 ms

571d67cb-de3d-41af-8c0a-06a53d490466.woff

571d67cb-de3d-41af-8c0a-06a53d490466.woff

22 ms

UC3ZEjagJi85gF9qFaBgIIidMZaDCgb76Cj_Fd30HHc.woff

UC3ZEjagJi85gF9qFaBgIIidMZaDCgb76Cj_Fd30HHc.woff

22 ms

UC3ZEjagJi85gF9qFaBgIMITpqSvb0EhPNqvdm-qG4s.woff

UC3ZEjagJi85gF9qFaBgIMITpqSvb0EhPNqvdm-qG4s.woff

22 ms

b8ee7e47-48e4-4b5b-8a74-cf02708fb54a.woff

b8ee7e47-48e4-4b5b-8a74-cf02708fb54a.woff

29 ms

92 ms

95 ms

104 ms

102 ms

99 ms

100 ms

128 ms

136 ms

149 ms

137 ms

136 ms

134 ms

deprecation-en.v5.html

deprecation-en.v5.html

8 ms

bolt-performance

bolt-performance

39 ms

deprecation-style.v5.css

deprecation-style.v5.css

10 ms

right-arrow.svg

right-arrow.svg

9 ms

Accessibility Review

ridinghorses.com accessibility score

84

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

button, link, and menuitem elements do not have accessible names.

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

Image elements do not have [alt] attributes

Best Practices

ridinghorses.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ridinghorses.com SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

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

ridinghorses.com

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