Tools & Wizards About Us
mediado.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

mediado.jp

株式会社メディアドゥ

Page Load Speed

12.8 sec in total

First Response

1.2 sec

Resources Loaded

10.8 sec

Page Rendered

827 ms

mediado.jp screenshot

About Website

Welcome to mediado.jp homepage info - get ready to check Mediado best content for Japan right away, or after learning these important things about mediado.jp

ひとつでも多くのコンテンツを、ひとりでも多くの人へ。

Visit mediado.jp

Key Findings

We analyzed Mediado.jp page load time and found that the first response time was 1.2 sec and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

mediado.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.925

3/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

www.mediado.jp

1236 ms

base.css

676 ms

base_add.css

354 ms

jquery-1.11.1.min.js

1232 ms

media_do.common.js

549 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 80% of them (47 requests) were addressed to the original Mediado.jp, 7% (4 requests) were made to S.ytimg.com and 3% (2 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Mediado.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 525.7 kB (14%)

Content Size

3.7 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mediado.jp 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. 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 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 21.7 kB

  • Original 29.0 kB
  • After minification 26.1 kB
  • After compression 7.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. 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 21.7 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 64.4 kB

  • Original 3.1 MB
  • After minification 3.0 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. Mediado images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 220.9 kB

  • Original 357.4 kB
  • After minification 355.5 kB
  • After compression 136.6 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 220.9 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 218.7 kB

  • Original 263.5 kB
  • After minification 259.2 kB
  • After compression 44.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. Mediado.jp needs all CSS files to be minified and compressed as it can save up to 218.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (16%)

Requests Now

56

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.mediado.jp

www.mediado.jp

1236 ms

base.css

base.css

676 ms

base_add.css

base_add.css

354 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

1232 ms

media_do.common.js

media_do.common.js

549 ms

youtube_control.js

youtube_control.js

367 ms

iframe_api

iframe_api

54 ms

ga.js

ga.js

35 ms

header_logo_001.png

header_logo_001.png

6675 ms

header_btn_Inquiry.png

header_btn_Inquiry.png

6673 ms

header_icon_file.gif

header_icon_file.gif

6674 ms

content_top_title.png

content_top_title.png

6676 ms

content_top_mainimg.jpg

content_top_mainimg.jpg

6683 ms

content_about_artwork.png

content_about_artwork.png

6678 ms

content_about_mainimg.jpg

content_about_mainimg.jpg

6688 ms

content_about_bottom_side.png

content_about_bottom_side.png

6676 ms

content_about_bottom_img.png

content_about_bottom_img.png

6677 ms

separate_title_market.png

separate_title_market.png

6680 ms

content_market_page1_img1.png

content_market_page1_img1.png

6680 ms

content_market_source.png

content_market_source.png

6678 ms

content_market_mainimg2.jpg

content_market_mainimg2.jpg

6689 ms

content_market_page2_img1.png

content_market_page2_img1.png

6685 ms

content_market_mainimg1.jpg

content_market_mainimg1.jpg

6686 ms

separate_title_advantage.png

separate_title_advantage.png

6683 ms

content_advantage_page1_img.jpg

content_advantage_page1_img.jpg

6689 ms

content_advantage_page2_img.jpg

content_advantage_page2_img.jpg

6690 ms

content_advantage_page3_img.jpg

content_advantage_page3_img.jpg

6693 ms

content_advantage_page4_img.jpg

content_advantage_page4_img.jpg

6692 ms

content_advantage_navi.png

content_advantage_navi.png

6690 ms

separate_title_results.png

separate_title_results.png

6689 ms

content_results_page1_img.jpg

content_results_page1_img.jpg

6693 ms

content_results_page2_img.jpg

content_results_page2_img.jpg

6694 ms

content_results_navi.png

content_results_navi.png

6692 ms

separate_title_elibrary.png

separate_title_elibrary.png

6691 ms

content_elibrary_title1.png

content_elibrary_title1.png

6693 ms

content_elibrary_mainimg1.jpg

content_elibrary_mainimg1.jpg

6697 ms

content_elibrary_page2_img.png

content_elibrary_page2_img.png

6694 ms

content_elibrary_title3.png

content_elibrary_title3.png

6693 ms

content_elibrary_page3_img.png

content_elibrary_page3_img.png

6696 ms

content_elibrary_page4_img.png

content_elibrary_page4_img.png

6695 ms

separate_title_grobal.png

separate_title_grobal.png

6693 ms

content_grobal_page1_img.png

content_grobal_page1_img.png

6694 ms

content_grobal_mainimg1.jpg

content_grobal_mainimg1.jpg

6697 ms

content_grobal_page2_img.png

content_grobal_page2_img.png

6696 ms

__utm.gif

__utm.gif

14 ms

www-widgetapi.js

www-widgetapi.js

18 ms

RGNcr9oQ60U

RGNcr9oQ60U

48 ms

content_grobal_page3_img1.png

content_grobal_page3_img1.png

843 ms

content_grobal_page3_btn.png

content_grobal_page3_btn.png

336 ms

content_grobal_page3_img2.png

content_grobal_page3_img2.png

888 ms

content_grobal_page3_img3.png

content_grobal_page3_img3.png

921 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

5 ms

www-embed-player.js

www-embed-player.js

30 ms

base.js

base.js

52 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

34 ms

ad_status.js

ad_status.js

31 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

30 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

31 ms

pageNavi_btn_white.png

pageNavi_btn_white.png

354 ms

Accessibility Review

mediado.jp accessibility score

93

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

Best Practices

mediado.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

mediado.jp SEO score

86

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

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

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 Mediado.jp 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 Mediado.jp 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

mediado.jp

Open Graph description is not detected on the main page of Mediado. 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: