3.2 sec in total
651 ms
1.8 sec
736 ms
Visit prerace.com now to see the best up-to-date Prerace content and also check out these interesting facts you probably never knew about prerace.com
Event calendar and registration for endurance events, including triathlon, nordic, running and bike events.
Visit prerace.comWe analyzed Prerace.com page load time and found that the first response time was 651 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
prerace.com performance score
651 ms
25 ms
59 ms
47 ms
44 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Prerace.com, 11% (7 requests) were made to Pr_img.s3.amazonaws.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (651 ms) relates to the external source Getevent.com.
Page size can be reduced by 340.4 kB (30%)
1.1 MB
789.3 kB
In fact, the total size of Prerace.com main page is 1.1 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. Images take 640.9 kB which makes up the majority of the site volume.
Potential reduce by 56.9 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 10.6 kB, which is 14% 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 56.9 kB or 77% of the original size.
Potential reduce by 11.0 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. Prerace images are well optimized though.
Potential reduce by 91.1 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 91.1 kB or 46% of the original size.
Potential reduce by 181.4 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. Prerace.com needs all CSS files to be minified and compressed as it can save up to 181.4 kB or 84% of the original size.
Number of requests can be reduced by 23 (39%)
59
36
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prerace. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.getevent.com
651 ms
css
25 ms
bootstrap.css
59 ms
jquery-ui-1.8.4.custom.css
47 ms
jquery.fancybox-1.3.1.css
44 ms
layout.css
50 ms
jquery.min.js
29 ms
page.add-your-event.css
57 ms
conversion.js
19 ms
jquery-ui.min.js
36 ms
bootstrap.min.js
147 ms
jquery.ui.datepicker.js
156 ms
validate.js
145 ms
jquery.fancybox-1.3.1.js
153 ms
site.global.js
153 ms
page.add-your-event.js
153 ms
icon_mtb.png
151 ms
160 ms
footerFB.jpg
409 ms
all.js
339 ms
analytics.js
118 ms
icon_bike.png
139 ms
icon_multi.png
139 ms
icon_multibike.png
118 ms
slide-breckepic.jpg
166 ms
testimonial-mikemac-head.jpg
118 ms
bg-getevent-cf.png
118 ms
bg-header.png
117 ms
logo-getevent.png
116 ms
bg-fiber.png
116 ms
screenshot-sunshine2014.png
181 ms
screenshot-donations.png
115 ms
screenshot-products.png
163 ms
screenshot-manage-participants.png
161 ms
screenshot-partipant-info.png
163 ms
screenshot-reports.png
162 ms
screenshot-reports-status.png
161 ms
screenshot-whitelabel.png
197 ms
screenshot-volunteer.png
182 ms
screenshot-pricing.png
180 ms
screenshot-categories.png
182 ms
screenshot-categories-chart.png
181 ms
screenshot-usac.png
194 ms
jorge-mug.jpg
221 ms
screenshot-event-sales.png
250 ms
screenshot-volunteer-cp.png
222 ms
screenshot-products-jersey.png
221 ms
screenshot-resources-timing.png
215 ms
logo-getevent-mono.png
218 ms
footerTwitter.jpg
353 ms
u-WUoqrET9fUeobQW7jkRSZ2oysoEQEeKwjgmXLRnTc.ttf
106 ms
DXI1ORHCpsQm3Vp6mXoaTY3LH2FgLjViKkqswU-xtII.ttf
127 ms
MTP_ySUJH_bn48VBG8sNSo3LH2FgLjViKkqswU-xtII.ttf
153 ms
k3k702ZOKiLJc3WVjuplzI3LH2FgLjViKkqswU-xtII.ttf
146 ms
ui-bg_flat_75_ffffff_40x100.png
547 ms
glyphicons-halflings-regular.woff
148 ms
collect
29 ms
collect
93 ms
69 ms
130 ms
xd_arbiter.php
212 ms
xd_arbiter.php
422 ms
nr-892.min.js
27 ms
ping
58 ms
e8d5306cbf
45 ms
prerace.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prerace.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 Prerace.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.
prerace.com
Open Graph description is not detected on the main page of Prerace. 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: