4.6 sec in total
727 ms
3.7 sec
226 ms
Welcome to decopatch.jp homepage info - get ready to check Decopatch best content right away, or after learning these important things about decopatch.jp
薄い紙をちぎってのりで貼るだけ!フランスうまれのデコレーションツール「デコパッチ(décopatch)」
Visit decopatch.jpWe analyzed Decopatch.jp page load time and found that the first response time was 727 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
decopatch.jp performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value5.6 s
18/100
25%
Value6.3 s
42/100
10%
Value70 ms
99/100
30%
Value0.021
100/100
15%
Value4.9 s
78/100
10%
727 ms
517 ms
391 ms
385 ms
1121 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 87% of them (41 requests) were addressed to the original Decopatch.jp, 11% (5 requests) were made to Google.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Decopatch.jp.
Page size can be reduced by 435.8 kB (29%)
1.5 MB
1.1 MB
In fact, the total size of Decopatch.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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 9.5 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 9.5 kB or 77% of the original size.
Potential reduce by 322.8 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, Decopatch needs image optimization as it can save up to 322.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 77.0 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 77.0 kB or 85% of the original size.
Potential reduce by 26.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. Decopatch.jp needs all CSS files to be minified and compressed as it can save up to 26.5 kB or 83% of the original size.
Number of requests can be reduced by 15 (33%)
46
31
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Decopatch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
decopatch.jp
727 ms
app.css
517 ms
thickbox.css
391 ms
jquery.bxslider.css
385 ms
slide_01.jpg
1121 ms
slide_02.jpg
1310 ms
slide_03.jpg
1351 ms
slide_04.jpg
1307 ms
slide_05.jpg
1344 ms
slide_06.jpg
1210 ms
jquery.min.js
71 ms
jquery.slidescroll.js
1137 ms
jquery.lazyload.js
1216 ms
common.js
1321 ms
thickbox.js
1323 ms
mousewheel.min.js
1327 ms
scrollbar.js
1365 ms
jsapi
57 ms
index.js
1374 ms
jquery.bxslider.js
1388 ms
slide_07.jpg
1873 ms
slide_08.jpg
1505 ms
heading_news.png
1511 ms
copyright.png
1555 ms
sprite.png
1186 ms
logo.png
1180 ms
gnavi_01.png
1309 ms
gnavi_02.png
1314 ms
gnavi_03.png
1363 ms
gnavi_04.png
1351 ms
gnavi_05.png
1375 ms
gnavi_06.png
1493 ms
gnavi_07.png
1498 ms
fnavi_01.png
1525 ms
fnavi_02.png
1553 ms
fnavi_03.png
1566 ms
16 ms
default+en.css
3 ms
default+en.I.js
5 ms
loadingAnimation.gif
617 ms
bx_loader.gif
621 ms
btn_prev.png
627 ms
btn_next.png
642 ms
banner_01.png
1069 ms
banner_02.png
1087 ms
banner_03.png
985 ms
Gfeeds
382 ms
decopatch.jp accessibility score
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
Links do not have a discernible name
decopatch.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
decopatch.jp SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Decopatch.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 Decopatch.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.
decopatch.jp
Open Graph description is not detected on the main page of Decopatch. 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: