Tools & Wizards About Us
matomedia.jp screenshot

Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

matomedia.jp

美容アイテムまとめでぃあ

Page Load Speed

7.7 sec in total

First Response

640 ms

Resources Loaded

6.8 sec

Page Rendered

170 ms

matomedia.jp screenshot

About Website

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

iPhoneアプリまとめ 目的別におすすめiPhoneアプリがすぐわかる モバイルルーター徹底比較 速度・エリア・料金でモバイル通信サービスを徹底比較。 有名脱毛サロンの噂 有名エステサロンを覆面調査で徹底検証！どのエステが良かったのか？

Visit matomedia.jp

Key Findings

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

Performance Metrics

matomedia.jp performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.197

62/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

matomedia.jp

640 ms

www.matomedia.jp

1479 ms

btt.js

348 ms

style.css

699 ms

color.css

350 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 50% of them (34 requests) were addressed to the original Matomedia.jp, 10% (7 requests) were made to Apis.google.com and 4% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source F00-243.046.137.203.fs-user.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.0 kB (58%)

Content Size

330.5 kB

After Optimization

139.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Matomedia.jp main page is 330.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 152.4 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 22.7 kB

  • Original 30.9 kB
  • After minification 29.4 kB
  • After compression 8.2 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 22.7 kB or 73% of the original size.

Image Optimization

-27%

Potential reduce by 21.0 kB

  • Original 78.9 kB
  • After minification 58.0 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. Obviously, Matomedia needs image optimization as it can save up to 21.0 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 90.8 kB

  • Original 152.4 kB
  • After minification 142.8 kB
  • After compression 61.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 90.8 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 56.5 kB

  • Original 68.3 kB
  • After minification 50.1 kB
  • After compression 11.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. Matomedia.jp needs all CSS files to be minified and compressed as it can save up to 56.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

64

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

matomedia.jp

matomedia.jp

640 ms

www.matomedia.jp

www.matomedia.jp

1479 ms

btt.js

btt.js

348 ms

style.css

style.css

699 ms

color.css

color.css

350 ms

doc.css

doc.css

591 ms

jquery.js

jquery.js

1029 ms

comment-reply.js

comment-reply.js

408 ms

microkids-related-posts-default.css

microkids-related-posts-default.css

521 ms

plugin.css

plugin.css

523 ms

datatables.css

datatables.css

612 ms

plusone.js

plusone.js

90 ms

bookmark_button.js

bookmark_button.js

363 ms

widgets.js

widgets.js

5 ms

widget.js

widget.js

60 ms

ga.js

ga.js

55 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

48 ms

button-only.gif

button-only.gif

212 ms

button_new18a.png

button_new18a.png

47 ms

logo.gif

logo.gif

211 ms

top_on.jpg

top_on.jpg

210 ms

purpose.jpg

purpose.jpg

228 ms

concept.jpg

concept.jpg

229 ms

category.jpg

category.jpg

211 ms

adpolicy.jpg

adpolicy.jpg

361 ms

reviewer.jpg

reviewer.jpg

361 ms

top_ttl01.gif

top_ttl01.gif

360 ms

top_bnr01.gif

top_bnr01.gif

3271 ms

top_bnr02.gif

top_bnr02.gif

398 ms

top_bnr03.gif

top_bnr03.gif

409 ms

top_ttl02.gif

top_ttl02.gif

536 ms

logo_iphone.png

logo_iphone.png

537 ms

logo_mobile.png

logo_mobile.png

538 ms

logo_netprint.png

logo_netprint.png

596 ms

logo_car.png

logo_car.png

614 ms

logo_lan.png

logo_lan.png

707 ms

logo_tochibaikyaku.gif

logo_tochibaikyaku.gif

711 ms

logo_kasai.png

logo_kasai.png

712 ms

logo_hoken.png

logo_hoken.png

794 ms

logo_sun.png

logo_sun.png

818 ms

btn_pageTop.gif

btn_pageTop.gif

879 ms

all.js

all.js

174 ms

h4_icon.gif

h4_icon.gif

3789 ms

search.png

search.png

872 ms

__utm.gif

__utm.gif

23 ms

433 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

15 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

17 ms

fastbutton

fastbutton

104 ms

like.php

like.php

168 ms

postmessageRelay

postmessageRelay

87 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

36 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

38 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

39 ms

api.js

api.js

58 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

90 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

69 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

101 ms

69 ms

xd_arbiter.php

xd_arbiter.php

142 ms

xd_arbiter.php

xd_arbiter.php

265 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

281 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

316 ms

jot

jot

86 ms

reset.css

reset.css

169 ms

entry-button.css

entry-button.css

170 ms

button-counter.gif

button-counter.gif

7 ms

ping

ping

32 ms

Accessibility Review

matomedia.jp accessibility score

63

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

matomedia.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 doesn't use 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 Matomedia.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 Matomedia.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

matomedia.jp

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