Tools & Wizards About Us
tbs-blog.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

tbs-blog.com

TBSテレビ

Page Load Speed

5.9 sec in total

First Response

314 ms

Resources Loaded

5.2 sec

Page Rendered

385 ms

tbs-blog.com screenshot

About Website

Welcome to tbs-blog.com homepage info - get ready to check Tbs Blog best content for Japan right away, or after learning these important things about tbs-blog.com

TBSテレビが放送する番組情報満載の公式サイトです。TBSが放送するテレビ番組の予告やあらすじなど、テレビ番組情報はこちらから！

Visit tbs-blog.com

Key Findings

We analyzed Tbs-blog.com page load time and found that the first response time was 314 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

tbs-blog.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value25.2 s

0/100

25%

SI (Speed Index)

Value15.1 s

1/100

10%

TBT (Total Blocking Time)

Value5,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value36.5 s

0/100

10%

Network Requests Diagram

tbs-blog.com

314 ms

www.tbs.co.jp

894 ms

reset.css

316 ms

gh_responsive.css

340 ms

g_footer.css

333 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tbs-blog.com, 84% (46 requests) were made to Tbs.co.jp and 5% (3 requests) were made to Web-jp.ad-v.jp. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Tbs.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 783.1 kB (53%)

Content Size

1.5 MB

After Optimization

705.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tbs-blog.com 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. 35% of websites need less resources to load. Javascripts take 852.2 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 18.7 kB

  • Original 26.4 kB
  • After minification 25.2 kB
  • After compression 7.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 18.7 kB or 71% of the original size.

Image Optimization

-4%

Potential reduce by 19.4 kB

  • Original 463.3 kB
  • After minification 443.9 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. Tbs Blog images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 622.5 kB

  • Original 852.2 kB
  • After minification 781.5 kB
  • After compression 229.7 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 622.5 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 122.5 kB

  • Original 146.7 kB
  • After minification 126.5 kB
  • After compression 24.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. Tbs-blog.com needs all CSS files to be minified and compressed as it can save up to 122.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (64%)

Requests Now

53

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tbs-blog.com

tbs-blog.com

314 ms

www.tbs.co.jp

www.tbs.co.jp

894 ms

reset.css

reset.css

316 ms

gh_responsive.css

gh_responsive.css

340 ms

g_footer.css

g_footer.css

333 ms

idx_carousel.css

idx_carousel.css

335 ms

idx.css

idx.css

353 ms

idx_timetable.css

idx_timetable.css

371 ms

idx_pickup.css

idx_pickup.css

470 ms

idx_newsi.css

idx_newsi.css

504 ms

functional.css

functional.css

500 ms

idx_modal.css

idx_modal.css

512 ms

common.js

common.js

527 ms

gh_responsive.js

gh_responsive.js

554 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

943 ms

flowplayer.min.js

flowplayer.min.js

874 ms

flowplayer.dashjs.min.js

flowplayer.dashjs.min.js

1200 ms

bn_responsive.js

bn_responsive.js

675 ms

gh_ie8.js

gh_ie8.js

699 ms

logger.js

logger.js

910 ms

gh_smp.js

gh_smp.js

578 ms

plugin_idx.js

plugin_idx.js

685 ms

g_footer.js

g_footer.js

718 ms

idx_wnew.js

idx_wnew.js

759 ms

idx_pickup.js

idx_pickup.js

850 ms

idx_timetable.js

idx_timetable.js

884 ms

idx_newsi.js

idx_newsi.js

893 ms

sscrolling.js

sscrolling.js

940 ms

idx_carousel_bxslider.js

idx_carousel_bxslider.js

943 ms

idx_carousel.js

idx_carousel.js

1015 ms

cover.png

cover.png

346 ms

gh_bg_pc.svg

gh_bg_pc.svg

350 ms

gh_parts.svg

gh_parts.svg

344 ms

gh_boobo.png

gh_boobo.png

348 ms

cm8adam_1_call.js

cm8adam_1_call.js

184 ms

detect

detect

361 ms

browserDataDetect.js

browserDataDetect.js

511 ms

detected

detected

512 ms

PCbanner1010.jpg

PCbanner1010.jpg

355 ms

idx_pc_bg.svg

idx_pc_bg.svg

359 ms

idx_boobo.png

idx_boobo.png

370 ms

idx_line.png

idx_line.png

354 ms

idx_icons.svg

idx_icons.svg

354 ms

tbstop_201602291825.jpg

tbstop_201602291825.jpg

533 ms

di2_bg_ill_w.png

di2_bg_ill_w.png

172 ms

idx_parts.svg

idx_parts.svg

169 ms

idx_newsi_bg.png

idx_newsi_bg.png

172 ms

di2_bg_dot_w.svg

di2_bg_dot_w.svg

165 ms

gf_dotline.png

gf_dotline.png

195 ms

gf_sns.png

gf_sns.png

331 ms

gf_parts.svg

gf_parts.svg

327 ms

gf_logos.png

gf_logos.png

334 ms

gf_pagetop.png

gf_pagetop.png

332 ms

tver_300x250.jpg

tver_300x250.jpg

119 ms

gif

gif

182 ms

Accessibility Review

tbs-blog.com accessibility score

94

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

tbs-blog.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tbs-blog.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 Tbs-blog.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 Tbs-blog.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

tbs-blog.com

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