Tools & Wizards About Us
tennislounge.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

tennislounge.com

日本最大級のテニススクール【テニスラウンジ】公式サイト

Page Load Speed

8.6 sec in total

First Response

630 ms

Resources Loaded

6.9 sec

Page Rendered

1 sec

tennislounge.com screenshot

About Website

Click here to check amazing Tennislounge content for Japan. Otherwise, check out these important facts you probably never knew about tennislounge.com

テニスラウンジは愛知,岐阜,三重,大阪,滋賀,兵庫,奈良,埼玉,札幌,沖縄にある日本最大級のテニススクールです。テニスが初めての方はもちろん、テニス初級者から上級者の方まで幅広いコースをご用意。丁寧で楽しいテニスレッスンが受けられます。お子さまの習い事にも是非。親子のコースもご用意しておりますのでまずはお近くのテニススクールへ体験レッスンにお越しください。

Visit tennislounge.com

Key Findings

We analyzed Tennislounge.com page load time and found that the first response time was 630 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

tennislounge.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value20.8 s

0/100

25%

SI (Speed Index)

Value24.0 s

0/100

10%

TBT (Total Blocking Time)

Value3,750 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value33.8 s

0/100

10%

Network Requests Diagram

tennislounge.com

630 ms

tennislounge.com

777 ms

js

73 ms

gtm.js

125 ms

jquery-1.9.0.min.js

358 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 84% of them (87 requests) were addressed to the original Tennislounge.com, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Tennislounge.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 238.2 kB (6%)

Content Size

3.7 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tennislounge.com main page is 3.7 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. 65% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 32.9 kB

  • Original 42.9 kB
  • After minification 38.6 kB
  • After compression 10.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 32.9 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 118.4 kB

  • Original 3.4 MB
  • After minification 3.3 MB

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. Tennislounge images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 78.6 kB

  • Original 265.1 kB
  • After minification 265.0 kB
  • After compression 186.5 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 78.6 kB or 30% of the original size.

CSS Optimization

-29%

Potential reduce by 8.3 kB

  • Original 28.9 kB
  • After minification 28.9 kB
  • After compression 20.6 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. Tennislounge.com needs all CSS files to be minified and compressed as it can save up to 8.3 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (30%)

Requests Now

97

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tennislounge.com

tennislounge.com

630 ms

tennislounge.com

tennislounge.com

777 ms

js

js

73 ms

gtm.js

gtm.js

125 ms

jquery-1.9.0.min.js

jquery-1.9.0.min.js

358 ms

reset.css

reset.css

520 ms

cmn.css

cmn.css

533 ms

jquery.bxslider.js

jquery.bxslider.js

709 ms

bxslider.js

bxslider.js

535 ms

jquery.bxslider.css

jquery.bxslider.css

535 ms

links.js

links.js

543 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

863 ms

cmn.js

cmn.js

710 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

711 ms

colorbox.css

colorbox.css

714 ms

jquery_bxslider_min.js

jquery_bxslider_min.js

719 ms

top.css

top.css

883 ms

top.css

top.css

885 ms

style.min.css

style.min.css

923 ms

styles.css

styles.css

926 ms

jquery.min.js

jquery.min.js

1074 ms

jquery-migrate.min.js

jquery-migrate.min.js

1033 ms

si_captcha.js

si_captcha.js

1059 ms

css2

css2

29 ms

jquery.form.min.js

jquery.form.min.js

1061 ms

scripts.js

scripts.js

1064 ms

wp-embed.min.js

wp-embed.min.js

1067 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

371 ms

analytics.js

analytics.js

24 ms

tracking.js

tracking.js

1101 ms

menu.png

menu.png

213 ms

but01.png

but01.png

213 ms

but02.png

but02.png

214 ms

but03.png

but03.png

210 ms

but04.png

but04.png

210 ms

but05.png

but05.png

356 ms

but06.png

but06.png

377 ms

but07.png

but07.png

375 ms

logo.png

logo.png

378 ms

logo-sp.png

logo-sp.png

375 ms

but08.png

but08.png

375 ms

but10.png

but10.png

508 ms

but09.png

but09.png

551 ms

sns_insta.png

sns_insta.png

552 ms

sns_youtube.png

sns_youtube.png

553 ms

HP_cp.png

HP_cp.png

908 ms

banner-tl.jpg

banner-tl.jpg

910 ms

56e092d51b9e59aae36c3b3d59fd8de4.png

56e092d51b9e59aae36c3b3d59fd8de4.png

678 ms

nishiharu.png

nishiharu.png

902 ms

banner-kashiiteriha.jpg

banner-kashiiteriha.jpg

1082 ms

point1.png

point1.png

727 ms

but01.png

but01.png

851 ms

point2.png

point2.png

905 ms

point1_b.png

point1_b.png

1023 ms

point2_b.png

point2_b.png

1077 ms

but02.png

but02.png

1081 ms

photo01.jpg

photo01.jpg

1084 ms

point3.png

point3.png

1087 ms

photo02.jpg

photo02.jpg

1192 ms

photo03.jpg

photo03.jpg

1253 ms

photo04.jpg

photo04.jpg

1258 ms

map.png

map.png

1614 ms

bn_trial.png

bn_trial.png

1616 ms

title_sns.png

title_sns.png

1264 ms

sdk.js

sdk.js

182 ms

sns_insta02.png

sns_insta02.png

1353 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

308 ms

collect

collect

52 ms

sns_youtube02.png

sns_youtube02.png

1240 ms

1f3be.svg

1f3be.svg

70 ms

sdk.js

sdk.js

20 ms

foot_ws.png

foot_ws.png

1233 ms

collect

collect

85 ms

foot_lo.png

foot_lo.png

1241 ms

foot_sk.png

foot_sk.png

1332 ms

foot_fa.png

foot_fa.png

1402 ms

foot_gk.png

foot_gk.png

1408 ms

57 ms

foot_bbl.png

foot_bbl.png

1274 ms

foot_ig.png

foot_ig.png

1340 ms

foot_tl.png

foot_tl.png

1415 ms

foot_pc.png

foot_pc.png

1422 ms

foot_coq.png

foot_coq.png

1421 ms

foot_tennibits.png

foot_tennibits.png

1424 ms

bn_recruit.png

bn_recruit.png

1671 ms

bg_foot02.png

bg_foot02.png

1337 ms

logo02.png

logo02.png

1556 ms

bn_foot01.png

bn_foot01.png

1740 ms

btn_top.png

btn_top.png

1423 ms

bg_but.png

bg_but.png

1373 ms

bg_dot01.png

bg_dot01.png

1248 ms

icon-btn.png

icon-btn.png

1371 ms

bg_dot03.png

bg_dot03.png

1372 ms

bg01.jpg

bg01.jpg

1398 ms

bg02.jpg

bg02.jpg

2798 ms

bg03.jpg

bg03.jpg

1515 ms

bg_sns.png

bg_sns.png

1537 ms

bg_foot.jpg

bg_foot.jpg

1405 ms

tracking.js

tracking.js

1061 ms

x-gm-ttr-api-redirect-location

x-gm-ttr-api-redirect-location

867 ms

scenario.js

scenario.js

171 ms

access

access

1099 ms

scenario.js

scenario.js

1199 ms

cmn_sp.css

cmn_sp.css

180 ms

Accessibility Review

tennislounge.com accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

tennislounge.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tennislounge.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tennislounge.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Tennislounge.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

tennislounge.com

Open Graph data is detected on the main page of Tennislounge. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: