9.6 sec in total
2.2 sec
7.2 sec
280 ms
Welcome to matilda.co.jp homepage info - get ready to check Matilda best content right away, or after learning these important things about matilda.co.jp
目黒区青葉台(中目黒)にあるフラワーショップ「Matilda」のオフィシャルサイトです。こだわり抜いた花や洗練された花器、インパクトあるアレンジメント、ブーケなどをお届けします。
Visit matilda.co.jpWe analyzed Matilda.co.jp page load time and found that the first response time was 2.2 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
matilda.co.jp performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value27.9 s
0/100
25%
Value8.6 s
17/100
10%
Value120 ms
97/100
30%
Value0.01
100/100
15%
Value5.7 s
69/100
10%
2191 ms
18 ms
34 ms
343 ms
331 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 62% of them (32 requests) were addressed to the original Matilda.co.jp, 23% (12 requests) were made to I.pinimg.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Matilda.co.jp.
Page size can be reduced by 176.3 kB (4%)
4.0 MB
3.9 MB
In fact, the total size of Matilda.co.jp main page is 4.0 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 3.9 MB which makes up the majority of the site volume.
Potential reduce by 27.4 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 27.4 kB or 86% of the original size.
Potential reduce by 132.6 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. Matilda images are well optimized though.
Potential reduce by 50 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 16.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. Matilda.co.jp needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 79% of the original size.
Number of requests can be reduced by 13 (27%)
49
36
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Matilda. 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 JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
matilda.co.jp
2191 ms
css
18 ms
css
34 ms
style.css
343 ms
jquery.bxslider.css
331 ms
jquery.min.js
7 ms
jquery.bxslider.min.js
508 ms
jquery.tipsy.js
340 ms
analytics.js
24 ms
19f7b335ec7bc1829c40007c4f2464e4.jpg
227 ms
backgroundtest.jpg
513 ms
background.png
4470 ms
icon_instagram.png
509 ms
icon_facebook.gif
171 ms
icon_pinterest.gif
340 ms
pointicon.gif
341 ms
top_20160720_1.jpg
2562 ms
key6.jpg
847 ms
key5.jpg
852 ms
top_20160720_2.jpg
3045 ms
key1.jpg
854 ms
key7.jpg
2371 ms
top_20160720_3.jpg
2212 ms
key8.jpg
1196 ms
key4.jpg
1543 ms
staff.gif
1715 ms
howtoorder.gif
1886 ms
staffwanted.gif
2057 ms
facebookbanner2.gif
2228 ms
blog.gif
2382 ms
matildashop.gif
2399 ms
footerlogo.gif
2539 ms
1c32b1ffa756b076416ab8028203f66b.jpg
81 ms
736820b419779b9f490c2a2770a6341b.jpg
172 ms
1f4f3fdf71462dbd20448d105a42dc62.jpg
166 ms
e66e86ac8e22cfb420fe43e8c9480adb.jpg
199 ms
3c2cccb899f7bdc0f54864d18b9b98b0.jpg
81 ms
d84403d4cf7f380a12caf77f0917bc6a.jpg
312 ms
b89b1d4d72e914d09369f1386fbb4c04.jpg
183 ms
f6a0b8cfceae9cc5daf0bdd2ef1992a7.jpg
293 ms
9c633c27a5ae6efef208a492a3e68fc0.jpg
288 ms
1546cb68ca4d0d8a3c3d8ec84f30c790.jpg
341 ms
3aad0a35bb3af000759c689964b5c05e.jpg
370 ms
pinterest.png
2535 ms
calback.png
2722 ms
tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf
52 ms
MwQubh3o1vLImiwAVvYawgcf2eVeqlq9.ttf
56 ms
collect
26 ms
calline.png
2650 ms
bx_loader.gif
2664 ms
controls.png
2672 ms
js
64 ms
matilda.co.jp accessibility score
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
matilda.co.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
matilda.co.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
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Matilda.co.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 Matilda.co.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.
matilda.co.jp
Open Graph data is detected on the main page of Matilda. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: