13.3 sec in total
700 ms
12.1 sec
486 ms
Visit stpride.jp now to see the best up-to-date ST PRIDE content and also check out these interesting facts you probably never knew about stpride.jp
くせ毛や髪のエイジングなどの髪の悩みに本気で向き合った、シャンプーやトリートメントなどのヘアケア商品を扱うST.PRIDE(セントプライド)です。ネット通販での購入もできます。
Visit stpride.jpWe analyzed Stpride.jp page load time and found that the first response time was 700 ms and then it took 12.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
stpride.jp performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value3.3 s
68/100
25%
Value8.4 s
18/100
10%
Value220 ms
88/100
30%
Value0.31
38/100
15%
Value3.9 s
88/100
10%
700 ms
335 ms
343 ms
379 ms
359 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 73% of them (27 requests) were addressed to the original Stpride.jp, 16% (6 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (11.1 sec) belongs to the original domain Stpride.jp.
Page size can be reduced by 96.5 kB (6%)
1.5 MB
1.4 MB
In fact, the total size of Stpride.jp main page is 1.5 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. 25% of websites need less resources to load. Images take 1.4 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. This page needs HTML code to be minified as it can gain 2.6 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 12.7 kB or 76% of the original size.
Potential reduce by 1.5 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. ST PRIDE images are well optimized though.
Potential reduce by 63.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 63.3 kB or 65% of the original size.
Potential reduce by 18.9 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. Stpride.jp needs all CSS files to be minified and compressed as it can save up to 18.9 kB or 79% of the original size.
Number of requests can be reduced by 15 (50%)
30
15
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ST PRIDE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for CSS and as a result speed up the page load time.
stpride.jp
700 ms
sp_global.css
335 ms
image_color.css
343 ms
pride_text.css
379 ms
product_page.css
359 ms
navi_pc_pride.css
361 ms
navi_sp_pride.css
386 ms
aos.css
41 ms
fadein.css
503 ms
css2
42 ms
st_pride.png
583 ms
instagram_noir.png
584 ms
facebook_noir.png
584 ms
shop_noir.png
584 ms
st_pride_picto.png
585 ms
st_pride_jaune.png
701 ms
st_pride.png
701 ms
aos.js
17 ms
jquery.min.js
18 ms
instagram.png
538 ms
facebook.png
604 ms
st_pride_blanc.png
605 ms
filet_petit.png
264 ms
stpride_image.jpg
1704 ms
filet.png
375 ms
top_prod1.png
1688 ms
top_prod2.png
11067 ms
top_prod3.png
1303 ms
top_prod4.png
1699 ms
st_pride_click.png
554 ms
online_shop.jpg
1584 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubD.woff
43 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75g.woff
125 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75g.woff
184 ms
HTxwL3I-JCGChYJ8VI-L6OO_au7B4-Lw_3I.woff
124 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7MV3w.woff
123 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQV3w.woff
121 ms
stpride.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
stpride.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
Browser errors were logged to the console
stpride.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stpride.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stpride.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.
stpride.jp
Open Graph description is not detected on the main page of ST PRIDE. 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: