Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

theresponse.jp

The_Response ザ・レスポンス

Page Load Speed

5.8 sec in total

First Response

800 ms

Resources Loaded

4.3 sec

Page Rendered

659 ms

theresponse.jp screenshot

About Website

Visit theresponse.jp now to see the best up-to-date The Response content for Japan and also check out these interesting facts you probably never knew about theresponse.jp

ザ・レスポンスは、小さな会社が実践で使える、ダイレクト・レスポンス・マーケティングの情報をお届けするサイトです。広告、マーケティングのメッカ、米国のノウハウを日本に合うようにローカライズしてお届けしています。

Visit theresponse.jp

Key Findings

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

Performance Metrics

theresponse.jp performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

www.theresponse.jp

800 ms

import.css

149 ms

index.css

299 ms

typesquare.js

239 ms

smartRollover.js

628 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 75% of them (77 requests) were addressed to the original Theresponse.jp, 5% (5 requests) were made to Google-analytics.com and 5% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Theresponse.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 376.6 kB (15%)

Content Size

2.6 MB

After Optimization

2.2 MB

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

HTML Optimization

-82%

Potential reduce by 53.4 kB

  • Original 65.1 kB
  • After minification 53.7 kB
  • After compression 11.7 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 11.4 kB, which is 17% 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 53.4 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 141.2 kB

  • Original 2.2 MB
  • After minification 2.1 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. The Response images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 124.2 kB

  • Original 213.4 kB
  • After minification 210.3 kB
  • After compression 89.2 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 124.2 kB or 58% of the original size.

CSS Optimization

-84%

Potential reduce by 57.8 kB

  • Original 68.8 kB
  • After minification 67.7 kB
  • After compression 11.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. Theresponse.jp needs all CSS files to be minified and compressed as it can save up to 57.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (22%)

Requests Now

98

After Optimization

76

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

Accessibility Review

theresponse.jp accessibility score

73

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

Links do not have a discernible name

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

theresponse.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

theresponse.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 uses 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 Theresponse.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 Theresponse.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

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