6.1 sec in total
549 ms
4.6 sec
944 ms
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.jpWe analyzed Theresponse.jp page load time and found that the first response time was 549 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
theresponse.jp performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value14.1 s
0/100
25%
Value10.9 s
6/100
10%
Value2,510 ms
4/100
30%
Value0.006
100/100
15%
Value17.0 s
4/100
10%
549 ms
169 ms
332 ms
123 ms
333 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 69% of them (80 requests) were addressed to the original Theresponse.jp, 8% (9 requests) were made to Static.xx.fbcdn.net and 6% (7 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Theresponse.jp.
Page size can be reduced by 574.7 kB (8%)
7.3 MB
6.7 MB
In fact, the total size of Theresponse.jp main page is 7.3 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. 70% of websites need less resources to load. Images take 7.0 MB which makes up the majority of the site volume.
Potential reduce by 60.6 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.3 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 60.6 kB or 82% of the original size.
Potential reduce by 445.3 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. The Response images are well optimized though.
Potential reduce by 64.3 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 64.3 kB or 38% of the original size.
Potential reduce by 4.5 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 4.5 kB or 40% of the original size.
Number of requests can be reduced by 36 (32%)
113
77
The browser has sent 113 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 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.theresponse.jp
549 ms
import.css
169 ms
index.css
332 ms
typesquare.js
123 ms
smartRollover.js
333 ms
jquery-1.7.2.min.js
501 ms
jquery.smoothScroll.js
333 ms
fixHeight.js
337 ms
jquery.cookie.list.js
335 ms
conversion.js
72 ms
s_retargeting.js
338 ms
reset.css
333 ms
module.css
332 ms
common.css
332 ms
nav.css
334 ms
s_retargeting.js
803 ms
logo.png
174 ms
btn_fb_s.png
173 ms
btn_tw_s.png
173 ms
btn_yt_s.png
174 ms
btn_pd_s.png
171 ms
8204f37ae0b35383e222689524b39c4a-498x280.png
704 ms
be4af4bd626841be5fbfce9f8b9dda24.png
1551 ms
200406.png
1388 ms
b9e847a828753d7c0b2a7c88158aa1a2.png
1718 ms
eae7e01102df010c98f6955da545c0fc.png
1241 ms
400kosasa_top.png
1007 ms
my-eye.jpg
965 ms
mamiya-e.jpg
1007 ms
harada-e.jpg
1240 ms
img_resouces01.png
1240 ms
img_resouces02.png
1391 ms
img_resouces03.png
1392 ms
IMG_0649.jpg
1891 ms
11.jpg
1562 ms
a_20151218031711.jpg
1563 ms
TSMC-member-with-customer_1511.jpg
1728 ms
thum.jpg
1715 ms
thum1.jpg
1734 ms
icon_play.png
1734 ms
no_image.png
1882 ms
a11b4bb3ba448d1fa402ac3dc62cc91f-2.jpg
1887 ms
a11b4bb3ba448d1fa402ac3dc62cc91f-1.jpg
1898 ms
a11b4bb3ba448d1fa402ac3dc62cc91f.jpg
1903 ms
a11b4bb3ba448d1fa402ac3dc62cc91f-3.jpg
1901 ms
a11b4bb3ba448d1fa402ac3dc62cc91f-2.jpg
2049 ms
img_aboutus01.png
2053 ms
img_aboutus02.png
2055 ms
img_guest01.png
2065 ms
img_guest02.png
2068 ms
img_guest03.png
2069 ms
49 ms
img_guest04.png
2206 ms
sdk.js
22 ms
gtm.js
61 ms
sdk.js
4 ms
60 ms
57 ms
analytics.js
8 ms
collect
28 ms
collect
29 ms
collect
9 ms
js
48 ms
img_guest06.png
2053 ms
img_guest07.png
2053 ms
img_guest08.png
2065 ms
img_guest11.png
2065 ms
img_guest12.png
2068 ms
fbevents.js
10 ms
img_fujioka.png
1653 ms
gtm.js
230 ms
collect
194 ms
collect
24 ms
page.php
61 ms
img_guest14.png
1404 ms
collect
17 ms
analytics.js
6 ms
img_team.jpg
1386 ms
icon_tblank.png
1398 ms
collect
14 ms
js
126 ms
FfF4P4SqcfL.css
13 ms
RsWZ-myCkRn.js
25 ms
teTZ2tZqwkq.js
51 ms
71nLmDRGsWE.js
54 ms
qnn7MVQZYOT.js
52 ms
5hjr18zii08.js
53 ms
zYzGplAqD4J.js
53 ms
p55HfXW__mM.js
51 ms
ga-audiences
189 ms
351780874_180698551631765_8634108595447166137_n.jpg
152 ms
351469468_116132981499989_1461001699789219143_n.jpg
135 ms
UXtr_j2Fwe-.png
103 ms
IMG_0809-498x498.jpg
1165 ms
IMG_1747-498x498.jpg
1167 ms
IMG_3707-1-498x498.jpg
1310 ms
IMG_0775-498x498.jpg
1170 ms
Summit-498x498.jpg
1169 ms
IMG_8522-498x498.jpg
1185 ms
IMG_3458-1-e1470296597294-498x498.jpg
1024 ms
FullSizeRender_5-498x498.jpg
1014 ms
btn_fb.png
1155 ms
btn_tw.png
1007 ms
btn_yt.png
1009 ms
btn_pd.png
1011 ms
loading.gif
1010 ms
bg_a80.png
1009 ms
arrow_blog01.png
1001 ms
bg_a70.png
1003 ms
bg_resouces.png
1001 ms
img_resouces01_o.png
1008 ms
img_resouces02_o.png
1009 ms
img_resouces03_o.png
1009 ms
arrow_podcast.png
1000 ms
arrow_guest01.png
1003 ms
icon_pt.png
1002 ms
theresponse.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
theresponse.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
theresponse.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
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.
theresponse.jp
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: