5.4 sec in total
518 ms
4.6 sec
260 ms
Click here to check amazing Putti content. Otherwise, check out these important facts you probably never knew about putti.jp
PuttiGroupは美容という仕事を通じて、地域の皆様や社会に貢献出来るよう日々努力を重ねております。
Visit putti.jpWe analyzed Putti.jp page load time and found that the first response time was 518 ms 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.
putti.jp performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value3.5 s
64/100
25%
Value7.6 s
25/100
10%
Value0 ms
100/100
30%
Value0.025
100/100
15%
Value3.4 s
93/100
10%
518 ms
956 ms
1326 ms
194 ms
389 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 73% of them (22 requests) were addressed to the original Putti.jp, 23% (7 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Putti.jp.
Page size can be reduced by 48.3 kB (27%)
178.4 kB
130.1 kB
In fact, the total size of Putti.jp main page is 178.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 139.0 kB which makes up the majority of the site volume.
Potential reduce by 8.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.9 kB, which is 23% 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 8.7 kB or 70% of the original size.
Potential reduce by 17.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. Obviously, Putti needs image optimization as it can save up to 17.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 22.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. Putti.jp needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 83% of the original size.
Number of requests can be reduced by 4 (25%)
16
12
The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Putti. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for CSS and as a result speed up the page load time.
putti.jp
518 ms
putti.jp
956 ms
www.putti.jp
1326 ms
import.css
194 ms
jquery-1.10.2.min.js
389 ms
jquery.easing.js
504 ms
heightLine.js
505 ms
script_all.js
504 ms
590 ms
reset.css
508 ms
base.css
388 ms
style.css
807 ms
notosansjapanese.css
23 ms
logo.png
232 ms
putti.jpg
497 ms
putti.png
230 ms
couleur.jpg
496 ms
couleur.png
230 ms
sign.jpg
825 ms
pgtop.png
346 ms
putti_exicon.png
349 ms
couleur_exicon.png
386 ms
nav-spc01.png
482 ms
NotoSansJP-Light.woff
76 ms
NotoSansJP-Thin.woff
191 ms
NotoSansJP-DemiLight.woff
192 ms
NotoSansJP-Regular.woff
114 ms
NotoSansJP-Medium.woff
116 ms
NotoSansJP-Bold.woff
120 ms
NotoSansJP-Black.woff
193 ms
putti.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
putti.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
putti.jp SEO score
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 Putti.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 Putti.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.
putti.jp
Open Graph data is detected on the main page of Putti. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: