Access dq10matome.com. ??Ѳ???Ƭ??Ƭ-??????´?Ƭ?ۿ???ַ-?????վ????Ӱ??Ƭ

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value21.1 s

0/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

dq10matome.com

2126 ms

template.css

518 ms

site.css

544 ms

import.js

547 ms

c2.js

360 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 10% of them (11 requests) were addressed to the original Dq10matome.com, 15% (17 requests) were made to Parts.blog.livedoor.jp and 13% (14 requests) were made to Blogroll.livedoor.net. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Dq10matome.com.

Content Size

1.5 MB

After Optimization

1.1 MB

In fact, the total size of Dq10matome.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. 50% of websites need less resources to load. Images take 974.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 111.1 kB

Original 130.2 kB
After minification 110.1 kB
After compression 19.1 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 20.1 kB, which is 15% 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 111.1 kB or 85% of the original size.

Image Optimization

-7%

Potential reduce by 65.6 kB

Original 974.1 kB
After minification 908.5 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. Dq 10 Matome images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 222.2 kB

Original 366.2 kB
After minification 345.6 kB
After compression 144.0 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 222.2 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 60.5 kB

Original 73.2 kB
After minification 55.0 kB
After compression 12.7 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. Dq10matome.com needs all CSS files to be minified and compressed as it can save up to 60.5 kB or 83% of the original size.

Requests Now

109

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

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

High

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

High

Document doesn't use legible font sizes

Language and Encoding

Language Detected

EL
Language Claimed

JA
Encoding

UTF-8

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

dq10matome.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

??Ѳ???Ƭ??Ƭ-??????´?Ƭ?ۿ???ַ-?????վ????Ӱ??Ƭ

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

dq10matome.com

template.css

site.css

import.js

c2.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

dq10matome.com

template.css

site.css

import.js

c2.js

smartphone.js

header.js

blogroll.js

ads.js

widgets.js

adsense_top.js

ldblog_calendar_plugin.js

template_6thgen.css

default2.css

kadomaru.css

rank.php

dq10matome.js

popular_articles_with_image_plugin.js

jquery-1.7.1.min.js

design.js

gpt.js

ga.js

icon.jpg

K_ZVm7Cc_bigger.jpeg

rranking.gif

twitter.jpg

bg.gif

logo_blog_premium.png

to_pagetop.png

c

logo_livedoor.gif

logo_blog.gif

head.jpg

entry_icon.png

calendar_icon.png

roll_data

roll_data

roll_data

adcore.js

adcore_pc.js

pubads_impl_81.js

__utm.gif

adcore_pc_inline.js