10.1 sec in total
2.2 sec
7.1 sec
725 ms
Welcome to hortiman.com homepage info - get ready to check Hortiman best content right away, or after learning these important things about hortiman.com
Visit hortiman.comWe analyzed Hortiman.com page load time and found that the first response time was 2.2 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hortiman.com performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value4.1 s
47/100
25%
Value3.7 s
86/100
10%
Value500 ms
57/100
30%
Value0
100/100
15%
Value4.4 s
84/100
10%
2247 ms
750 ms
506 ms
509 ms
506 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 35% of them (45 requests) were addressed to the original Hortiman.com, 19% (25 requests) were made to Live-hortiman.time.ly and 5% (6 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Hortiman.com.
Page size can be reduced by 2.5 MB (54%)
4.7 MB
2.2 MB
In fact, the total size of Hortiman.com main page is 4.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 908.2 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 908.2 kB or 64% of the original size.
Potential reduce by 42.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. Hortiman images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 71% of the original size.
Potential reduce by 166.0 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. Hortiman.com needs all CSS files to be minified and compressed as it can save up to 166.0 kB or 84% of the original size.
Number of requests can be reduced by 80 (68%)
118
38
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hortiman. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
hortiman.com
2247 ms
wp-emoji-release.min.js
750 ms
styles.css
506 ms
social_widget.css
509 ms
tpg-get-posts-style.css
506 ms
css
25 ms
style.css
751 ms
style.css
706 ms
jquery.js
1484 ms
jquery-migrate.min.js
761 ms
wop.css
755 ms
custom-css-frontend.css
949 ms
output.css
996 ms
daves-wordpress-live-search_default_gray.css
995 ms
js.php
1147 ms
addthis_widget.js
16 ms
style-display-gallery.css
555 ms
material-design-iconic-font.min.css
1310 ms
magnific-popup.css
791 ms
underscore.min.js
792 ms
daves-wordpress-live-search.min.js
800 ms
excanvas.compiled.js
1132 ms
spinners.min.js
1131 ms
jquery.form.min.js
1331 ms
scripts.js
1176 ms
smoothscroll.js
1330 ms
wp-embed.min.js
1329 ms
imagesloaded.pkgd.min.js
1329 ms
site_gallery.js
1398 ms
ga.js
9 ms
__utm.gif
49 ms
big-p-button.png
71 ms
947 ms
Hortipedia_Social_Profile.png
599 ms
Screen-Shot-2014-04-03-at-11.35.13-am.png
815 ms
ginko.jpg
1347 ms
H210-0468-300x78.png
600 ms
Screen-Shot-2015-11-18-at-2.11.14-PM-219x300.png
1620 ms
Screen-Shot-2015-11-18-at-2.11.29-PM-216x300.png
1793 ms
Screen-Shot-2015-11-18-at-2.11.50-PM-218x300.png
1175 ms
HAL0050_MREC_Static-300x250.jpg
813 ms
Screen-Shot-2015-01-22-at-3.30.49-pm-150x150.png
1099 ms
Charlie-275x300.jpeg
1098 ms
facebook.png
1558 ms
twitter.png
1558 ms
youtube.png
1558 ms
instagram.png
1558 ms
tumblr.png
1801 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
13 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
13 ms
cj2hUnSRBhwmSPr9kS589-LrC4Du4e_yfTJ8Ol60xk0.ttf
39 ms
c92rD_x0V1LslSFt3-QEpmsGzsqhEorxQDpu60nfWEc.ttf
38 ms
QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf
38 ms
all.js
522 ms
count.js
134 ms
default
474 ms
count-data.js
336 ms
js_http.php
1903 ms
300lo.json
41 ms
all.js&version=v2.0
774 ms
widgets.js
154 ms
pinit00.png
25 ms
counter.5524cceca805eb4b9b2b.js
143 ms
sh.8e5f85691f9aaa082472a194.html
139 ms
ai1ec_js_widget.js
1377 ms
333 ms
icons.png
161 ms
1458478931568
436 ms
341 ms
shares.json
117 ms
shares.json
116 ms
shares.json
116 ms
shares.json
115 ms
shares.json
113 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
297 ms
xd_arbiter.php
331 ms
xd_arbiter.php
660 ms
combined.css
35 ms
smoothDivScroll.css
49 ms
jquery.min.js
55 ms
jquery.cycle.lite.js
94 ms
analytics.js
134 ms
10995075_1690986951160058_1522800348_n.jpg
378 ms
play_small.png
179 ms
12747679_716698201799990_725496384_n.jpg
591 ms
1389701_845440775578142_1905324342_n.jpg
627 ms
12543137_442477692622749_70591622_n.jpg
698 ms
12556105_962696377158695_1158267030_n.jpg
647 ms
12331529_419846758214888_454120751_n.jpg
636 ms
collect
9 ms
collect
87 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
128 ms
layers.e5ea973510bf60b3db41.js
128 ms
ajax-loader-3.gif
110 ms
373 ms
66 ms
nr-885.min.js
44 ms
jot.html
30 ms
a53393d12f
49 ms
33 ms
v3
61 ms
192 ms
calendar.js
259 ms
load_views.js
160 ms
event.js
179 ms
utils.js
159 ms
gmaps.js
158 ms
print.js
83 ms
agenda_view.js
79 ms
month_view.js
76 ms
frontend_utils.js
144 ms
select2_multiselect_helper.js
152 ms
twig.js
293 ms
agenda.js
163 ms
oneday.js
277 ms
month.js
176 ms
jquery_history.js
269 ms
jquery.tablescroller.js
218 ms
jquery.scrollTo.js
233 ms
bootstrap_datepicker.js
258 ms
alert.js
290 ms
jquery_cookie.js
312 ms
tab.js
307 ms
gmaps_helper.js
307 ms
output.css
249 ms
Ad.png
1238 ms
live-hortiman.time.ly
164 ms
live-hortiman.time.ly
1064 ms
wsmC9pGAAAAAAFSd7nXAAA=
4 ms
hortiman.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
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.
hortiman.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
hortiman.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hortiman.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Hortiman.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.
hortiman.com
Open Graph description is not detected on the main page of Hortiman. 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: