2.9 sec in total
217 ms
2 sec
690 ms
Click here to check amazing Hort Week content for United States. Otherwise, check out these important facts you probably never knew about hortweek.com
HortWeek has the latest news, jobs and technical advice for ornamental nurseries, edibles production, garden retailing, landscaping, parks, gardens, turf and arboriculture
Visit hortweek.comWe analyzed Hortweek.com page load time and found that the first response time was 217 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
hortweek.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value11.6 s
0/100
25%
Value7.5 s
27/100
10%
Value900 ms
32/100
30%
Value0.74
6/100
15%
Value15.4 s
7/100
10%
217 ms
360 ms
76 ms
65 ms
34 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 10% of them (12 requests) were addressed to the original Hortweek.com, 22% (28 requests) were made to Cached.imagescaler.hbpl.co.uk and 13% (17 requests) were made to E.visualdna.com. The less responsive or slowest element that took the longest time to load (703 ms) relates to the external source Offlinehbpl.hbpl.co.uk.
Page size can be reduced by 588.7 kB (39%)
1.5 MB
929.8 kB
In fact, the total size of Hortweek.com 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. 60% of websites need less resources to load. Images take 895.8 kB which makes up the majority of the site volume.
Potential reduce by 65.9 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 65.9 kB or 80% of the original size.
Potential reduce by 176.5 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, Hort Week needs image optimization as it can save up to 176.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 306.6 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 306.6 kB or 62% of the original size.
Potential reduce by 39.7 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. Hortweek.com needs all CSS files to be minified and compressed as it can save up to 39.7 kB or 81% of the original size.
Number of requests can be reduced by 58 (53%)
110
52
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hort Week. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
hortweek.com
217 ms
www.hortweek.com
360 ms
_Layout_Universal_LayoutMediaProvider_5DF45D99A54E6C040C765361F254E847.css
76 ms
modernizr_0F305161C0D22D7410DD392AC6408862.js
65 ms
jquery.min.js
34 ms
HortWeek_jobw_958x30v2--8.jpg
266 ms
hillsborough-20160226024243138.jpg
35 ms
btnSearch.png
19 ms
tileDarkGreen.png
23 ms
activeLi.png
20 ms
jobsDivider.gif
34 ms
jobsBkg.gif
30 ms
bkgPromo.png
34 ms
Norwich_MartinPearce_920p-20160226035308975.jpg
23 ms
handwateringsyngenta-20160226014157761.jpg
27 ms
download-20160226074532557.jpg
28 ms
download-2016022608565833.jpg
30 ms
Tesco-fp-aisle_Bownose_920p-20160225062322516.jpg
179 ms
download-20160229024840952.jpg
323 ms
download-20160229021927403.jpg
255 ms
cambridgepixabay-20160229023510127.jpg
257 ms
download-20160229013947747.jpg
324 ms
download-20160229012704767.jpg
255 ms
retail-201506030850428621-20160229124532402.JPG
308 ms
download-20160229021142886.jpg
500 ms
Coolings-Roses-004-20160205104933338.gif
285 ms
Coolings-Roses-004-20160125021230575.gif
285 ms
026_14154309RGB_A4-20160225103113512.jpg
284 ms
026_14262867-20160210110353833.jpg
343 ms
028_14115301RGB-20160128104614101.jpg
294 ms
072_peach-20160226081257905.jpg
319 ms
download-20160224041839613.jpg
328 ms
menu.png
176 ms
logo.gif
303 ms
logoSmall.gif
177 ms
facebook.png
177 ms
linkedin.png
178 ms
twitter.png
177 ms
googlePlus.png
190 ms
jobsLogo.gif
249 ms
HW-free-trial-ad2.gif
309 ms
HWKCustodianAwardLogo_v31.jpg
460 ms
175yearsWEB.jpg
703 ms
Landscape4places-xcol-promo.png
533 ms
pt_sans-regular.woff
38 ms
download-20160222031316516.jpg
324 ms
077_Wolstanton1-20160225105819515.jpg
302 ms
047_MowerWeibangVirtue53ProHW-2016021502124572.jpg
321 ms
050_MowerATT30inINFINIWithMattRainey-20160215015134261.jpg
468 ms
13_GreenTekDynaSeederHW-2016021801403770.jpg
305 ms
13_OtterbineAirFlo3HW-20160218040220655.jpg
319 ms
032_PentlandBiomass1-20160215025753232.jpg
325 ms
whatKitLogo.gif
218 ms
utag.js
56 ms
_Layout_Universal_LayoutMediaProviderCE76B8CDBFEA684F3DE0C6BA8E482090.js
17 ms
Classic-display-at-the-entrance-to-M...-20151209122248850.jpg
527 ms
logoHaymarket.png
210 ms
pt_sans-bold.woff
30 ms
pt_sans-narrow-bold.woff
15 ms
pt_sans-narrow-regular.woff
31 ms
robotoslab-regular.woff
67 ms
nr-852.min.js
26 ms
utag.1.js
11 ms
utag.64.js
10 ms
utag.80.js
3 ms
utag.81.js
9 ms
utag.83.js
9 ms
analytics.js
135 ms
gpt.js
10 ms
cc_af.js
133 ms
analytics.js
9 ms
8670df0cad
125 ms
pubads_impl_81.js
5 ms
ads
158 ms
ads
157 ms
ads
177 ms
ads
151 ms
ads
191 ms
ads
172 ms
ads
200 ms
ads
218 ms
ads
237 ms
ads
301 ms
ads
290 ms
ads
314 ms
ads
319 ms
container.html
44 ms
collect
24 ms
collect
102 ms
14495643781466453451
93 ms
14741417878014134915
76 ms
110 ms
17376843062205982972
83 ms
osd.js
34 ms
events
78 ms
10301538349944604486
45 ms
pixel
30 ms
GenericUserSync.ashx
24 ms
generic
21 ms
sync
45 ms
1
37 ms
sync
26 ms
15988768826595535575
17 ms
conversion
177 ms
generic
15 ms
conversion
169 ms
conversion
173 ms
import
173 ms
import
173 ms
import
175 ms
import
271 ms
conversion
277 ms
sync
8 ms
import
268 ms
import
277 ms
import
270 ms
sync
18 ms
conversion
269 ms
pixel
17 ms
conversion
334 ms
conversion
329 ms
import
328 ms
2981
21 ms
import
221 ms
import
212 ms
1
133 ms
hortweek.com 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
hortweek.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
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
hortweek.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hortweek.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Hortweek.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.
hortweek.com
Open Graph description is not detected on the main page of Hort Week. 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: