Tools & Wizards About Us
answer.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

answer.jp

アンサー・アンサー劇場終了のお知らせ

Page Load Speed

4.5 sec in total

First Response

644 ms

Resources Loaded

3.4 sec

Page Rendered

547 ms

answer.jp screenshot

About Website

Click here to check amazing Answer content for Japan. Otherwise, check out these important facts you probably never knew about answer.jp

Visit answer.jp

Key Findings

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

Performance Metrics

answer.jp performance score

0

Network Requests Diagram

answer.jp

644 ms

style.css

779 ms

analytics.js

95 ms

slogan_iphone_05.png

1000 ms

slogan_iphone_07.png

1011 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Answer.jp, 65% (11 requests) were made to Resource-answer.nanapiapps.com and 18% (3 requests) were made to D3o5jx8f2j6owm.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Resource-answer.nanapiapps.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 229.5 kB (20%)

Content Size

1.1 MB

After Optimization

918.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 4.8 kB

  • Original 6.8 kB
  • After minification 6.1 kB
  • After compression 2.0 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 4.8 kB or 71% of the original size.

Image Optimization

-10%

Potential reduce by 96.7 kB

  • Original 978.5 kB
  • After minification 881.8 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. Answer images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-90%

Potential reduce by 127.9 kB

  • Original 141.9 kB
  • After minification 94.0 kB
  • After compression 14.0 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. Answer.jp needs all CSS files to be minified and compressed as it can save up to 127.9 kB or 90% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Answer. According to our analytics all requests are already optimized.

Network Requests Diagram

answer.jp

answer.jp

644 ms

style.css

style.css

779 ms

analytics.js

analytics.js

95 ms

slogan_iphone_05.png

slogan_iphone_05.png

1000 ms

slogan_iphone_07.png

slogan_iphone_07.png

1011 ms

slogan_iphone_06.png

slogan_iphone_06.png

974 ms

bg_icons.png

bg_icons.png

440 ms

logo_type_answer.png

logo_type_answer.png

442 ms

header.png

header.png

1568 ms

btn_appstore.png

btn_appstore.png

481 ms

btn_googleplay.png

btn_googleplay.png

476 ms

banner_live_pr.png

banner_live_pr.png

628 ms

logo_answer.png

logo_answer.png

722 ms

icon_sns_twitter.png

icon_sns_twitter.png

578 ms

icon_sns_facebook.png

icon_sns_facebook.png

618 ms

banner_theater.png

banner_theater.png

935 ms

collect

collect

12 ms

SEO Factors

answer.jp SEO score

0

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 Answer.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 Answer.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

answer.jp

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