5.7 sec in total
703 ms
4.7 sec
298 ms
Click here to check amazing Hanasada content. Otherwise, check out these important facts you probably never knew about hanasada.com
目黒にある生花店『フラワーショップ花定』では、ハートツリー・胡蝶蘭・生花・お祝い花・葬儀花・ブーケ・観葉植物・季節の花などの販売を行っております。目黒駅より徒歩約8分でアクセスも便利です。通販も行っております。03-3491-4187ヨイハナまで。
Visit hanasada.comWe analyzed Hanasada.com page load time and found that the first response time was 703 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
hanasada.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value4.6 s
35/100
25%
Value11.6 s
4/100
10%
Value160 ms
94/100
30%
Value0.015
100/100
15%
Value8.0 s
42/100
10%
703 ms
292 ms
307 ms
961 ms
343 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 73% of them (91 requests) were addressed to the original Hanasada.com, 11% (14 requests) were made to Maps.googleapis.com and 6% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Hanasada.com.
Page size can be reduced by 853.8 kB (35%)
2.4 MB
1.6 MB
In fact, the total size of Hanasada.com main page is 2.4 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 10.3 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 10.3 kB or 71% of the original size.
Potential reduce by 93.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. Hanasada images are well optimized though.
Potential reduce by 707.9 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 707.9 kB or 72% of the original size.
Potential reduce by 42.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. Hanasada.com needs all CSS files to be minified and compressed as it can save up to 42.5 kB or 75% of the original size.
Number of requests can be reduced by 73 (62%)
118
45
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hanasada. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 54 to 1 for CSS and as a result speed up the page load time.
hanasada.com
703 ms
site.css
292 ms
page.css
307 ms
tieredworks_libs.js
961 ms
tieredworks_base.js
343 ms
tieredworks_ajax.js
373 ms
tieredworks_modules.js
592 ms
tieredworks_spry.js
1160 ms
ana.js
457 ms
tieredworks_exts.js
513 ms
base.css
270 ms
sitetheme.css
321 ms
theme.css
380 ms
pagelayout.css
443 ms
blockdesign.css
483 ms
modulestyle.css
457 ms
module_B000000002.css
374 ms
module_B000000007.css
174 ms
module_B000000025.css
154 ms
module_B000000308.css
222 ms
module_B000000325.css
306 ms
module_B000000326.css
344 ms
module_B000000327.css
356 ms
module_B000000328.css
418 ms
module_B000000331.css
458 ms
module_B000000332.css
514 ms
module_B000000333.css
516 ms
module_B000000335.css
558 ms
module_B000000336.css
538 ms
module_B000000338.css
613 ms
module_B000000339.css
608 ms
module_B000000340.css
684 ms
module_B000000353.css
676 ms
module_B000000462.css
683 ms
module_B000000463.css
744 ms
module_B000000464.css
759 ms
module_B000000513.css
808 ms
bg.jpg
163 ms
189 ms
navi_bg.jpg
147 ms
q100.jpg
344 ms
q101.jpg
305 ms
q102.jpg
394 ms
q103.jpg
292 ms
q104.jpg
323 ms
logo2.jpg
560 ms
q112.jpg
728 ms
q105.jpg
954 ms
index.html
471 ms
maps
55 ms
q106.jpg
662 ms
q108-.jpg
1051 ms
q110-.jpg
826 ms
clover_top.jpg
1131 ms
q115-.jpg
1518 ms
q114.jpg
1051 ms
news.jpg
958 ms
log.jpg
1233 ms
q111.jpg
1130 ms
f_clover_btn.jpg
1203 ms
stand_btn.jpg
1439 ms
voice_btn.jpg
1432 ms
r-navi2.jpg
1301 ms
fcbk.jpg
1338 ms
footer.jpg
1537 ms
index.php
1482 ms
embed
576 ms
page.css
1025 ms
js
78 ms
init_embed.js
34 ms
common.js
59 ms
map.js
77 ms
google4.png
35 ms
overlay.js
31 ms
util.js
116 ms
onion.js
109 ms
search_impl.js
115 ms
StaticMapService.GetMapImage
265 ms
stats.js
94 ms
openhand_8_8.cur
80 ms
ViewportInfoService.GetViewportInfo
57 ms
ViewportInfoService.GetViewportInfo
89 ms
kh
132 ms
transparent.png
37 ms
controls.js
43 ms
vt
151 ms
vt
144 ms
vt
136 ms
vt
159 ms
vt
146 ms
css
86 ms
entity11.png
43 ms
ViewportInfoService.GetViewportInfo
37 ms
mapcnt6.png
25 ms
tmapctrl.png
33 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
59 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
76 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
81 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
80 ms
AuthenticationService.Authenticate
12 ms
theme.css
162 ms
pagelayout.css
148 ms
blockdesign.css
199 ms
modulestyle.css
217 ms
module_B000000309.css
163 ms
module_B000000310.css
188 ms
module_B000000311.css
148 ms
module_B000000312.css
175 ms
module_B000000313.css
155 ms
module_B000000314.css
198 ms
module_B000000315.css
293 ms
module_B000000316.css
308 ms
module_B000000317.css
324 ms
module_B000000318.css
344 ms
module_B000000319.css
374 ms
module_B000000320.css
395 ms
module_B000000321.css
438 ms
module_B000000322.css
459 ms
module_B000000323.css
483 ms
module_B000000367.css
515 ms
module_B000000368.css
561 ms
module_B000000369.css
591 ms
module_B000000529.css
582 ms
news_bg.jpg
163 ms
index.php
190 ms
hanasada.com 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
hanasada.com 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
Page has valid source maps
hanasada.com 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hanasada.com 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 Hanasada.com 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.
hanasada.com
Open Graph description is not detected on the main page of Hanasada. 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: