Access polygraph.jp. POLYGRAPH

polygraph.jp screenshot

0

Performance
33

Accessibility

Visual factors better than
that of 18% of websites
67

Best Practices

More advanced features
available than in
24% of websites
64

SEO

Google-friendlier than
24% of websites

First Response

518 ms

Resources Loaded

11.6 sec

Page Rendered

2.1 sec

polygraph.jp screenshot

About Website

Welcome to polygraph.jp homepage info - get ready to check POLYGRAPH best content right away, or after learning these important things about polygraph.jp

Visit polygraph.jp

Key Findings

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

polygraph.jp

518 ms

menu_up.html

176 ms

menu_intro.html

340 ms

top_page.html

1590 ms

right.html

357 ms

Our browser made a total of 173 requests to load all elements on the main page. We found that 99% of them (171 requests) were addressed to the original Polygraph.jp, 1% (1 request) were made to Polygraph.sakura.ne.jp and 1% (1 request) were made to Tanzi.jp. The less responsive or slowest element that took the longest time to load (9.5 sec) relates to the external source Tanzi.jp.

Content Size

76.9 kB

After Optimization

51.3 kB

In fact, the total size of Polygraph.jp main page is 76.9 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. 40% of websites need less resources to load. Images take 76.0 kB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 417 B

Original 817 B
After minification 796 B
After compression 400 B

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 417 B or 51% of the original size.

Image Optimization

-33%

Potential reduce by 25.2 kB

Original 76.0 kB
After minification 50.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. Obviously, POLYGRAPH needs image optimization as it can save up to 25.2 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Now

172

After Optimization

149

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

Accessibility Issues

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

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

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

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Browser errors were logged to the console

Search Engine Optimization Advices

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Polygraph.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Polygraph.jp main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

polygraph.jp

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