2 sec in total
208 ms
1.4 sec
313 ms
Click here to check amazing Legacy TENNIS content for United States. Otherwise, check out these important facts you probably never knew about legacy.tennis.com
TENNIS.com - Live Scores, Tennis News, Player Ranking, and Complete Tournament Data.
Visit legacy.tennis.comWe analyzed Legacy.tennis.com page load time and found that the first response time was 208 ms and then it took 1.8 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.
legacy.tennis.com performance score
208 ms
329 ms
60 ms
39 ms
51 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Legacy.tennis.com, 45% (39 requests) were made to Cdn.tennis.com and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (375 ms) relates to the external source Securepubads.g.doubleclick.net.
Page size can be reduced by 2.2 MB (64%)
3.5 MB
1.2 MB
In fact, the total size of Legacy.tennis.com main page is 3.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. 80% 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. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 89.3 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 23.3 kB, which is 23% 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 89.3 kB or 87% of the original size.
Potential reduce by 52.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. Legacy TENNIS images are well optimized though.
Potential reduce by 1.5 MB
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 1.5 MB or 76% of the original size.
Potential reduce by 543.3 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. Legacy.tennis.com needs all CSS files to be minified and compressed as it can save up to 543.3 kB or 87% of the original size.
Number of requests can be reduced by 39 (51%)
76
37
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legacy TENNIS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
legacy.tennis.com
208 ms
www.tennis.com
329 ms
eiv0nll.js
60 ms
font-awesome.min.css
39 ms
modernizr-2.6.2-min.js
51 ms
jquery-1.11.3.min.js
29 ms
jquery-migrate-1.2.1.min.js
29 ms
jquery-ui.min.js
26 ms
selectivizr-min.js
42 ms
chosen.jquery.min.js
44 ms
main.css
115 ms
tag.js
138 ms
USTA_dil_v5.7_updated_final.js
112 ms
async_survey
111 ms
scores.css
110 ms
widgets_require.js
125 ms
css
28 ms
combined-min.js
8 ms
ads.js
5 ms
gpt.js
137 ms
beacon.js
119 ms
analytics.js
117 ms
dpm_536fb6934062440c464ca2eef82b0be8e6b36cc8.min.js
118 ms
bacon.min.js
108 ms
all.js
255 ms
tennis-logo-type.png
70 ms
sprite.png
58 ms
homepage.jpg
61 ms
homepage.jpg
63 ms
homepage.jpg
59 ms
homepage.jpeg
61 ms
photo-band.jpg
58 ms
photo-band.jpg
59 ms
photo-band.jpg
60 ms
gear-details-medium.jpg
61 ms
gear-details-medium.jpg
62 ms
photo-band.jpg
64 ms
photo-band.jpeg
62 ms
standard.jpeg
61 ms
search-form-submit.png
65 ms
small.jpg
62 ms
small.jpg
63 ms
small.jpg
62 ms
small.jpg
63 ms
small.jpg
64 ms
small.jpg
64 ms
Tennis_Footer_940X175_V4.jpg
65 ms
tennis-logo-type-small.png
64 ms
prompt_embed_static.js
60 ms
2016-03-01_livescores_new.json
286 ms
ad5Eb9g3F0I
159 ms
m
147 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
130 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
130 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
130 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
131 ms
pubads_impl_81.js
119 ms
collect
110 ms
homepage-thumbnail.jpg
51 ms
20087
115 ms
homepage-thumbnail.jpg
102 ms
homepage-thumbnail.jpg
104 ms
homepage-thumbnail.jpeg
104 ms
bkg-black-50.png
105 ms
231 ms
www-embed-player-vflQrT_sR.css
233 ms
www-embed-player.js
270 ms
base.js
343 ms
ads
375 ms
container.html
139 ms
20214
171 ms
index.php
166 ms
collect
123 ms
232 ms
caret-down.png
37 ms
flags-s7a4efe103c.png
82 ms
194 ms
xd_arbiter.php
181 ms
xd_arbiter.php
323 ms
pixel
43 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
94 ms
ad_status.js
172 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
92 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
151 ms
566569791132993527
118 ms
ads
89 ms
osd.js
24 ms
legacy.tennis.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Legacy.tennis.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Legacy.tennis.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.
legacy.tennis.com
Open Graph description is not detected on the main page of Legacy TENNIS. 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: