6.2 sec in total
1.3 sec
4.5 sec
414 ms
Welcome to stretchex.jp homepage info - get ready to check Stretchex best content for Japan right away, or after learning these important things about stretchex.jp
はじめてのストレッチ専門店なら『ストレチックス』(東京都文京区:新大塚・千石・白山・春日後楽園、東十条、東日本橋、北海道札幌、滋賀草津、山口、長崎諫早)。整体やマッサージが好き、運動不足な方にも人気!
Visit stretchex.jpWe analyzed Stretchex.jp page load time and found that the first response time was 1.3 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
stretchex.jp performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value6.8 s
7/100
25%
Value7.8 s
24/100
10%
Value330 ms
76/100
30%
Value0.682
8/100
15%
Value7.0 s
53/100
10%
1305 ms
192 ms
339 ms
340 ms
328 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 93% of them (56 requests) were addressed to the original Stretchex.jp, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Stretchex.jp.
Page size can be reduced by 230.7 kB (15%)
1.6 MB
1.4 MB
In fact, the total size of Stretchex.jp main page is 1.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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 12.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. 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 12.7 kB or 71% of the original size.
Potential reduce by 48.1 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. Stretchex images are well optimized though.
Potential reduce by 136.6 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 136.6 kB or 68% of the original size.
Potential reduce by 33.3 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. Stretchex.jp needs all CSS files to be minified and compressed as it can save up to 33.3 kB or 81% of the original size.
Number of requests can be reduced by 20 (35%)
57
37
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stretchex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
stretchex.jp
1305 ms
basic.css
192 ms
frame.css
339 ms
common.css
340 ms
contents.css
328 ms
jquery.js
521 ms
device.js
347 ms
fancybox.js
352 ms
whats-new.css
509 ms
fade.js
506 ms
analytics.js
43 ms
body.bg.jpg
169 ms
image01.png
336 ms
header.bg.jpg
170 ms
image02.png
322 ms
logo.png
175 ms
nav.btn.png
326 ms
contact.bg.png
363 ms
contact.btn.png
365 ms
content.bg.png
374 ms
256_image.jpg
1004 ms
255_image.jpg
1048 ms
254_image.jpg
894 ms
253_image.jpg
1030 ms
252_image.jpg
1041 ms
250_image.jpg
1033 ms
251_image.jpg
1233 ms
249_image.jpg
1341 ms
247_image.jpg
1552 ms
web_shinootsuka.png
1253 ms
web_kamiitabashi.png
1274 ms
top-exterior.jpg
2002 ms
top-interior.jpg
1737 ms
logo2.png
1430 ms
logo_small.png
1437 ms
information.bg.png
1530 ms
information.h.png
1573 ms
lead.img.png
1729 ms
why.png
1686 ms
varied.png
1692 ms
needs.png
1746 ms
footer.bg2.png
1851 ms
footer.lm.png
1858 ms
footer.bg.png
1877 ms
article.btn.png
1892 ms
anan.jpg
1918 ms
menu.h.png
2013 ms
collect
12 ms
collect
60 ms
jquery.fancybox.css
1893 ms
jquery.fancybox.js
1919 ms
movie2.jpg
2079 ms
ga-audiences
29 ms
access.bg.jpg
1969 ms
access.btn.png
1852 ms
recruit.jpg
1880 ms
merit.jpg
1863 ms
stretchnavi260_70.jpg
1894 ms
frame_s.css
177 ms
contents_s.css
196 ms
stretchex.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
Image elements do not have [alt] attributes
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.
stretchex.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
stretchex.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stretchex.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 Stretchex.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.
stretchex.jp
Open Graph description is not detected on the main page of Stretchex. 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: