22.7 sec in total
4.8 sec
17.7 sec
259 ms
Visit historicracing.co.za now to see the best up-to-date Historic Racing content and also check out these interesting facts you probably never knew about historicracing.co.za
Visit historicracing.co.zaWe analyzed Historicracing.co.za page load time and found that the first response time was 4.8 sec and then it took 17.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
historicracing.co.za performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value9.5 s
0/100
25%
Value20.4 s
0/100
10%
Value300 ms
79/100
30%
Value0.012
100/100
15%
Value17.7 s
4/100
10%
4758 ms
761 ms
1439 ms
1079 ms
1492 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 90% of them (112 requests) were addressed to the original Historicracing.co.za, 3% (4 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Secure.oneallcdn.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Historicracing.co.za.
Page size can be reduced by 97.7 kB (7%)
1.5 MB
1.4 MB
In fact, the total size of Historicracing.co.za main page is 1.5 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 665.8 kB which makes up the majority of the site volume.
Potential reduce by 73.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 73.7 kB or 80% of the original size.
Potential reduce by 12.4 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. Historic Racing images are well optimized though.
Potential reduce by 5.4 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.
Potential reduce by 6.2 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. Historicracing.co.za has all CSS files already compressed.
Number of requests can be reduced by 93 (82%)
114
21
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Historic Racing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 44 to 1 for CSS and as a result speed up the page load time.
www.historicracing.co.za
4758 ms
sdm_wp_styles.css
761 ms
dashicons.min.css
1439 ms
extra.min.css
1079 ms
style.min.css
1492 ms
style.css
1135 ms
links-shortcode.css
1142 ms
frontend.min.css
1143 ms
jquery.fancybox-1.3.4.css
1444 ms
font-awesome.min.css
1519 ms
css
27 ms
jquery.sidr.dark.min.css
1529 ms
slick.min.css
1526 ms
style.css
1807 ms
trigger_buttons.css
1811 ms
v4-shims.min.css
1870 ms
all.min.css
1902 ms
pagination_style.css
1909 ms
nextgen_basic_thumbnails.css
1916 ms
display.css
2172 ms
addthis_wordpress_public.min.css
2172 ms
um-modal.min.css
2250 ms
jquery-ui.min.css
2286 ms
tipsy.min.css
2294 ms
um-raty.min.css
2302 ms
fonticons-ii.min.css
2540 ms
fonticons-fa.min.css
2539 ms
select2.min.css
2629 ms
um-fileupload.min.css
2667 ms
default.min.css
2680 ms
default.date.min.css
2685 ms
default.time.min.css
2904 ms
common.min.css
2904 ms
um-styles.min.css
3008 ms
cropper.min.css
3049 ms
um-profile.min.css
3067 ms
um-account.min.css
3069 ms
addthis_widget.js
78 ms
um-misc.min.css
2900 ms
um-responsive.min.css
2514 ms
um-old-default.min.css
2313 ms
um-online.min.css
2305 ms
icons.css
2317 ms
shortcodes.css
2317 ms
jquery.min.js
2561 ms
jquery-migrate.min.js
2194 ms
sdm_wp_scripts.js
2272 ms
ajax.min.js
2302 ms
v4-shims.min.js
2316 ms
all.min.js
3846 ms
nextgen_basic_thumbnails.js
2204 ms
um-gdpr.min.js
2330 ms
jquery.t-countdown.js
2358 ms
common.js
2341 ms
lightbox_context.js
2452 ms
jquery.easing-1.3.pack.js
2445 ms
jquery.fancybox-1.3.4.pack.js
2344 ms
nextgen_fancybox_init.js
2414 ms
skip-link-focus-fix.min.js
2363 ms
jquery.cycle2.min.js
2435 ms
jquery.sidr.min.js
2431 ms
slick.min.js
2592 ms
custom.min.js
2429 ms
underscore-before.js
2458 ms
underscore.min.js
2454 ms
underscore-after.js
2415 ms
wp-util.min.js
2591 ms
wp-polyfill-inert.min.js
2669 ms
regenerator-runtime.min.js
2479 ms
wp-polyfill.min.js
2902 ms
hooks.min.js
2436 ms
i18n.min.js
2598 ms
tipsy.min.js
2668 ms
picker.min.js
2686 ms
picker.date.min.js
2496 ms
picker.time.min.js
2552 ms
common.min.js
2632 ms
cropper.min.js
2684 ms
common-frontend.min.js
2687 ms
um-modal.min.js
2694 ms
jquery-form.min.js
2538 ms
fileupload.js
2409 ms
um-functions.min.js
2583 ms
um-responsive.min.js
2665 ms
um-conditional.min.js
2515 ms
select2.full.min.js
2524 ms
library.js
772 ms
en.js
2342 ms
KFOmCnqEu92Fr1Mu7GxM.woff
53 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
64 ms
KFOkCnqEu92Fr1MmgVxGIzQ.woff
63 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
71 ms
wARDj0u
33 ms
um-raty.min.js
2307 ms
um-scripts.min.js
2539 ms
um-profile.min.js
2532 ms
um-account.min.js
2553 ms
shield-notbot.bundle.js
2387 ms
um-online.min.js
2316 ms
fontawesome-webfont.woff
2692 ms
fontawesome-webfont.woff
3176 ms
ionicons.woff
2926 ms
forkawesome-webfont.woff
3084 ms
129 ms
hrsa-theme-header.jpg
2298 ms
HRSA-3-Homepage-320x212.jpg
2298 ms
modern.css
638 ms
PDF.png
2546 ms
thumbs_RedStar-20191012-1424.jpg
2594 ms
thumbs_RedStar-20200307-0854.jpg
2415 ms
thumbs_RedStar-20200307-0921.jpg
2635 ms
thumbs_RedStar-20210306-1183.jpg
2665 ms
Charlies-Superspar-320x66.jpg
2686 ms
thumbs_DSC1433.jpg
2625 ms
thumbs_HRSA-Pursuit-4537.jpg
2631 ms
flat_w32_h32_wc_v1.css
97 ms
thumbs_HRSA-Racing-4993.jpg
2607 ms
thumbs_Zwartkops-20200131-3022.jpg
2597 ms
thumbs_Zwartkops-20201010-1596.jpg
2656 ms
flat_w32_h32_w_b_v2.png
572 ms
fancybox-x.png
1469 ms
fancybox.png
1466 ms
fancybox-y.png
1668 ms
blank.gif
1717 ms
historicracing.co.za accessibility score
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
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
historicracing.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
historicracing.co.za SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Historicracing.co.za 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 Historicracing.co.za 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.
historicracing.co.za
Open Graph description is not detected on the main page of Historic Racing. 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: