4.2 sec in total
311 ms
3.5 sec
440 ms
Visit horti.jp now to see the best up-to-date HORTI content for Japan and also check out these interesting facts you probably never knew about horti.jp
horti(ホルティ)は、花や植物を楽しむための情報をお届けするメディアです。花言葉や育て方など植物の基本情報から、ガーデニングのノウハウ、インテリアやプレゼントにおすすめの花束・アレンジメント・観葉植物の選び方まで、生活を彩る情報がいっぱい!
Visit horti.jpWe analyzed Horti.jp page load time and found that the first response time was 311 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 65% of websites can load faster.
horti.jp performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value7.8 s
3/100
25%
Value50.5 s
0/100
10%
Value84,070 ms
0/100
30%
Value0
100/100
15%
Value114.4 s
0/100
10%
311 ms
831 ms
103 ms
273 ms
867 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 23% of them (16 requests) were addressed to the original Horti.jp, 37% (26 requests) were made to Ddmxdtm74ysa7.cloudfront.net and 7% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Ddmxdtm74ysa7.cloudfront.net.
Page size can be reduced by 284.6 kB (41%)
686.7 kB
402.1 kB
In fact, the total size of Horti.jp main page is 686.7 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. 50% of websites need less resources to load. HTML takes 307.6 kB which makes up the majority of the site volume.
Potential reduce by 273.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 273.3 kB or 89% of the original size.
Potential reduce by 1.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. HORTI images are well optimized though.
Potential reduce by 9.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. This website has mostly compressed JavaScripts.
Potential reduce by 137 B
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. Horti.jp needs all CSS files to be minified and compressed as it can save up to 137 B or 28% of the original size.
Number of requests can be reduced by 25 (39%)
64
39
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HORTI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
horti.jp
311 ms
horti.jp
831 ms
analytics.js
103 ms
gtm.js
273 ms
6e14595c7e5825f8d55b3f0a27d94809_1456503106-135x135.jpg
867 ms
adsbygoogle.js
88 ms
content.php
253 ms
jquery.js
537 ms
modernizr.custom.min.js
633 ms
pc-header-logo.png
815 ms
bee.png
589 ms
search-icon@2x.png
610 ms
facebook-plugin-icon@2x.png
849 ms
pc-footer-logo.png
813 ms
39b9e3e8b618f942030bbc221c8b457a-135x135.jpg
846 ms
fe0f5518cd074b0814befca867ee1541_1456422281-135x135.jpg
245 ms
ad62926fc61cd37846c88ec89418030c_1456428216-135x135.jpg
286 ms
df4060545c42639641eaed37263e8ff4_1456419888-135x135.jpg
893 ms
a79c03f5affee622100798e7156b403a_1456419891-135x135.jpg
287 ms
d918ef8e65227c1e25022789673de913-135x135.jpg
285 ms
86ebb6e82a5475628b3f63f0bf0fd161-135x135.jpg
958 ms
c54a9568a230a05e28356d54d47b8d2a-135x135.jpg
1046 ms
4b842dad387d2c7fc457a2b601e80741_1456408689-135x135.jpg
957 ms
795a9d1124f1525a964fcbcbfd8e44d4_1454509143-135x135.jpg
1440 ms
cddd94cc023a0eaa213644aae164c901_1456337923-135x135.jpg
1454 ms
4de44d9ebd56a738deb9ea8881ec928e_1456337920-135x135.jpg
1546 ms
37ecc132c08ed6f187c2ae8595ad120b_1456331868-135x135.jpg
1611 ms
d9c54c164873c1b5de75b48bdb8bf027_1456331870-135x135.jpg
1601 ms
shutterstock_221053765-90x90.jpg
1674 ms
f79ccaee8139f5151fe4fd9022a7c936-90x90.jpg
1438 ms
a8be45da2331ea1ec0308b6e3c8be1f8-90x90.jpg
1440 ms
f72b0cf929fc66e917b5041e34e3690f-90x90.jpg
1440 ms
f9edb5054c62158bc6629405555984a5-90x90.jpg
1441 ms
45c887e56bb26e69da4f37466b3836a31-90x90.jpg
1443 ms
shutterstock_237972811-90x90.jpg
2091 ms
f8df18891f781e0112b6f4d2615d4c6e-90x90.jpg
1451 ms
b0d5afdb08b3adee8d345009ea8b19b0-90x90.jpg
1459 ms
shutterstock_251219941-90x90.jpg
1463 ms
0847efd14ebc00ed722feedd72414e03_1455479706.png
1475 ms
ca-pub-9032666777705730.js
73 ms
zrt_lookup.html
94 ms
show_ads_impl.js
107 ms
ajs.php
339 ms
collect
38 ms
collect
139 ms
ads
430 ms
osd.js
31 ms
ads
410 ms
jquery-migrate.min.js
292 ms
lg.php
225 ms
2998280568344544268
72 ms
abg.js
77 ms
m_js_controller.js
101 ms
googlelogo_color_112x36dp.png
68 ms
css
133 ms
s
5 ms
x_button_blue2.png
50 ms
ajax-load-more.min.js
163 ms
es-ad-inserter.js
198 ms
script.js
198 ms
scripts.js
214 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
34 ms
favicon
85 ms
nessie_icon_tiamat_white.png
23 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
28 ms
webfont.js
53 ms
css
15 ms
1wiHF6pWOa568Cj3p-anxC3USBnSvpkopQaUR-2r7iU.ttf
5 ms
wp-emoji-release.min.js
150 ms
ui
56 ms
horti.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
horti.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
horti.jp SEO score
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
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 Horti.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 Horti.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.
horti.jp
Open Graph data is detected on the main page of HORTI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: