40 sec in total
1.4 sec
22 sec
16.5 sec
Click here to check amazing Doctor Indy content. Otherwise, check out these important facts you probably never knew about doctorindy.com
JI500 - Johnson's Indy 500 at Doctorindy.com - Sharing Indianapolis 500 history and The Talk of Gasoline Alley since 1998
Visit doctorindy.comWe analyzed Doctorindy.com page load time and found that the first response time was 1.4 sec and then it took 38.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
doctorindy.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value6.1 s
12/100
25%
Value6.0 s
46/100
10%
Value3,280 ms
2/100
30%
Value0
100/100
15%
Value18.3 s
3/100
10%
1405 ms
16 ms
32 ms
30 ms
102 ms
Our browser made a total of 243 requests to load all elements on the main page. We found that 13% of them (32 requests) were addressed to the original Doctorindy.com, 14% (35 requests) were made to I0.wp.com and 9% (23 requests) were made to S.pubmine.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Ssl-market-east.smrtb.com.
Page size can be reduced by 276.3 kB (8%)
3.4 MB
3.1 MB
In fact, the total size of Doctorindy.com main page is 3.4 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. 75% 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 218.0 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 218.0 kB or 76% of the original size.
Potential reduce by 983 B
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. Doctor Indy images are well optimized though.
Potential reduce by 17.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 17.4 kB or 20% of the original size.
Potential reduce by 39.8 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. Doctorindy.com needs all CSS files to be minified and compressed as it can save up to 39.8 kB or 21% of the original size.
Number of requests can be reduced by 158 (71%)
224
66
The browser has sent 224 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doctor Indy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
doctorindy.com
1405 ms
wp-emoji-release.min.js
16 ms
style.css
32 ms
theme.css
30 ms
mediaelementplayer-legacy.min.css
102 ms
wp-mediaelement.min.css
101 ms
style-coblocks-1.css
35 ms
widget-text.css
35 ms
dashicons.min.css
108 ms
style.css
50 ms
latest.css
50 ms
css
120 ms
font-awesome.min.css
78 ms
slick.min.css
82 ms
slick-theme.min.css
71 ms
blocks.min.css
80 ms
style.css
58 ms
jetpack.css
70 ms
tiled-gallery.min.js
92 ms
jquery.min.js
108 ms
jquery-migrate.min.js
107 ms
regenerator-runtime.min.js
104 ms
wp-polyfill.min.js
108 ms
index.min.js
91 ms
index.min.js
91 ms
bilmur.min.js
106 ms
photon.min.js
88 ms
coblocks-animation.js
88 ms
jetpack-carousel.min.js
89 ms
skip-link-focus-fix.min.js
103 ms
navigation.min.js
102 ms
slick.min.js
112 ms
custom.min.js
102 ms
search-widget.js
100 ms
milestone.min.js
101 ms
intersection-observer.js
110 ms
lazy-images.js
110 ms
responsive-videos.min.js
109 ms
e-202240.js
111 ms
conf
455 ms
cropped-20130724123635096_0001.jpg
226 ms
WFBMpagoda.jpg
459 ms
btn_donateCC_LG.gif
324 ms
pixel.gif
326 ms
2023indy500big-1024x1024.jpg
317 ms
2022-indianapolis-500-logo-1.jpg
455 ms
DSCN3340.jpg
662 ms
DSCN3342_00001.jpg
611 ms
2021indy500.jpg
453 ms
2020-August-Indy-500-Logo.png
632 ms
dscn3272.jpg
609 ms
NIK_0012.jpg
788 ms
05-19-2021-Jake-and-Mike-talk-about-Tom-Carnegie-mp3-image.jpg
566 ms
foyt1961museum.jpg
1138 ms
mears1991museum.jpg
1650 ms
DSCN3357.jpg
1079 ms
NIK_4987.jpg
1167 ms
N20_1450_00001.jpg
1689 ms
DSCN3359.jpg
1222 ms
alunserjr1992.jpg
1510 ms
DSCN0867.jpg
1566 ms
photo_120597.jpg
1647 ms
NIK_0031.jpg
1744 ms
legendsbrickyard-788872068-1590170169469.jpg
1675 ms
indysnowclip.jpeg
1818 ms
NIK_3685.jpg
2303 ms
NightBeforethe500.jpg
1766 ms
tracksideck.jpg
1819 ms
polishing.jpg
1816 ms
bal1996-2.jpg
1861 ms
doorsga.jpg
1861 ms
2016-indianapolis-500-logo_1280x620-e1539375977411.jpg
1895 ms
1994by400-hires.jpg
1868 ms
nik_3242.jpg
2158 ms
pict0477.jpg
2067 ms
nik_3346.jpg
2243 ms
nik_3891.jpg
2184 ms
rahal-1986.jpg
2258 ms
AlIndyMeans.png
3986 ms
milestone_widget-4
338 ms
ata.js
26 ms
pixel
95 ms
tag.js
236 ms
uc.html
297 ms
user_sync.html
325 ms
user_sync.html
366 ms
prbds2s
415 ms
async_usersync.html
450 ms
user_sync.html
360 ms
usync.html
528 ms
checksync.php
703 ms
iframe
296 ms
jslog
97 ms
jslog
77 ms
all
19688 ms
30907
520 ms
match
400 ms
setuid
445 ms
sync
174 ms
match
417 ms
match
416 ms
PugMaster
540 ms
694 ms
URnmbSKM
514 ms
user_sync.html
189 ms
match
456 ms
usermatch
380 ms
match
423 ms
match
421 ms
pd
227 ms
match
400 ms
match
452 ms
usync.js
266 ms
match
325 ms
524 ms
0.gif
670 ms
8fb66763-e2ba-edbb-c589-7e4a9f010adc
441 ms
ny75r2x0
439 ms
us.gif
136 ms
match
400 ms
match
346 ms
us.gif
133 ms
match
402 ms
usersync
533 ms
usersync.aspx
551 ms
match
354 ms
us.gif
134 ms
us.gif
296 ms
demconf.jpg
242 ms
match
270 ms
us.gif
268 ms
pixel
267 ms
usersync
455 ms
usersync
455 ms
info2
247 ms
us.gif
245 ms
match
203 ms
engine
517 ms
usersync
446 ms
usersync
444 ms
pixel
319 ms
cksync.php
302 ms
cksync.php
407 ms
usersync
405 ms
cksync.php
504 ms
usersync
413 ms
us.gif
271 ms
usersync
366 ms
match
188 ms
cksync
433 ms
usg.gif
168 ms
usync.html
185 ms
usersync
311 ms
usersync
314 ms
us.gif
185 ms
cksync.php
380 ms
usermatchredir
179 ms
usersync
275 ms
usersync
292 ms
sd
159 ms
rum
212 ms
usync.html
179 ms
usersync
271 ms
tap.php
158 ms
cksync
289 ms
tap.php
204 ms
crum
200 ms
sd
117 ms
us.gif
97 ms
usync.html
130 ms
match
89 ms
sd
127 ms
crum
222 ms
us.gif
97 ms
sync
95 ms
dcm
116 ms
match
90 ms
1000.gif
141 ms
cksync.html
174 ms
match
83 ms
pixel
107 ms
crum
73 ms
match
151 ms
match
153 ms
cksync.php
158 ms
pixel
101 ms
cksync.php
133 ms
crum
90 ms
crum
89 ms
match
135 ms
cksync.php
201 ms
cksync.php
174 ms
usersync
71 ms
tap.php
55 ms
70 ms
usersync
52 ms
match
84 ms
usersync
48 ms
usersync
24 ms
ecm3
26 ms
cksync.php
46 ms
usersync
20 ms
match
18 ms
cksync.php
214 ms
cksync.php
101 ms
match
5 ms
match
6 ms
cksync.php
137 ms
ecm3
74 ms
PugMaster
20 ms
PugMaster
13 ms
p.gif
103 ms
info
63 ms
g.pixel
25 ms
generic
24 ms
usersync.aspx
33 ms
match
31 ms
Pug
135 ms
Pug
88 ms
Pug
90 ms
Pug
79 ms
Pug
124 ms
p.gif
58 ms
Pug
39 ms
Pug
41 ms
PugMaster
22 ms
Artemis
103 ms
sn.ashx
237 ms
pubmatic
118 ms
i.match
187 ms
usersync
51 ms
Pug
50 ms
Pug
51 ms
receive
45 ms
Pug
26 ms
qmap
38 ms
pixel
26 ms
pbmtc.gif
6 ms
Pug
12 ms
Pug
13 ms
Pug
12 ms
i.match
126 ms
sn.ashx
40 ms
doctorindy.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
doctorindy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
doctorindy.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doctorindy.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 Doctorindy.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.
doctorindy.com
Open Graph data is detected on the main page of Doctor Indy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: