Access nakata.net. nakata.net | 中田英寿（Hidetoshi Nakata）Official Site

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.803

5/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

nakata.net

1248 ms

import.css

328 ms

css

47 ms

all.css

42 ms

buddybar.css

332 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 90% of them (82 requests) were addressed to the original Nakata.net, 4% (4 requests) were made to Use.fontawesome.com and 2% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Nakata.net.

Content Size

2.7 MB

After Optimization

2.4 MB

In fact, the total size of Nakata.net main page is 2.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. 50% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 22.4 kB

Original 29.3 kB
After minification 28.3 kB
After compression 6.9 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.4 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 12.0 kB

Original 2.2 MB
After minification 2.2 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. Nakata images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 209.2 kB

Original 310.3 kB
After minification 279.5 kB
After compression 101.1 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 209.2 kB or 67% of the original size.

CSS Optimization

-76%

Potential reduce by 117.0 kB

Original 153.7 kB
After minification 120.3 kB
After compression 36.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. Nakata.net needs all CSS files to be minified and compressed as it can save up to 117.0 kB or 76% of the original size.

Requests Now

After Optimization

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nakata. 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 27 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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 semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

High

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

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

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

High

Links do not have descriptive text

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

High

Links are not crawlable

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 Nakata.net 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 Nakata.net 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

nakata.net

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

Report Summary

Performance

Accessibility

Best Practices

SEO

nakata.net | 中田英寿（Hidetoshi Nakata）Official Site

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

nakata.net

import.css

css

all.css

buddybar.css

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

nakata.net

import.css

css

all.css

buddybar.css

theme-my-login.css

polls-css.css

style.css

style.css

responsive.css

l10n.js

jquery.js

nakata_net.js

snbinder-0.5.3.js

jquery.bottom-1.0.js

jquery.upload-1.0.2.js

jquery.blockUI.js

global.js

cforms.css

cforms.js

swfobject.js

wpp.css

util.js

jquery.dropdownPlain.js

jquery.textarearesizer.compressed.js

jquery.ah-placeholder.js

jquery.jscrollpane.css

jquery.mousewheel.js

jquery.jscrollpane.min.js

jquery-ui.js

slick.css

slick-theme.css

jquery.min.js

common.js

slick.min.js

custom.js

common.css

contents.css

club.css

club2.css

pull.css

ie.css

single.css