4.6 sec in total
500 ms
3.9 sec
159 ms
Welcome to woodstock.co.nz homepage info - get ready to check Woodstock best content right away, or after learning these important things about woodstock.co.nz
Delivering fresh cut flowers throughout Wellington. New Zealand grown fresh cut flowers. Gift wrap bouquets
Visit woodstock.co.nzWe analyzed Woodstock.co.nz page load time and found that the first response time was 500 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
woodstock.co.nz performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value5.2 s
23/100
25%
Value7.0 s
32/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value4.4 s
83/100
10%
500 ms
906 ms
512 ms
217 ms
440 ms
Our browser made a total of 21 requests to load all elements on the main page. We found that 67% of them (14 requests) were addressed to the original Woodstock.co.nz, 19% (4 requests) were made to Images.growonline.co.nz and 10% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Images.growonline.co.nz.
Page size can be reduced by 90.7 kB (32%)
284.4 kB
193.8 kB
In fact, the total size of Woodstock.co.nz main page is 284.4 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. 20% of websites need less resources to load. Images take 137.3 kB which makes up the majority of the site volume.
Potential reduce by 5.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 5.9 kB or 62% of the original size.
Potential reduce by 43.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, Woodstock needs image optimization as it can save up to 43.5 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 24.3 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 24.3 kB or 21% of the original size.
Potential reduce by 16.9 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. Woodstock.co.nz needs all CSS files to be minified and compressed as it can save up to 16.9 kB or 82% of the original size.
Number of requests can be reduced by 5 (36%)
14
9
The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Woodstock. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
woodstock.co.nz
500 ms
woodstock.co.nz
906 ms
home.aspx
512 ms
modules.css
217 ms
presentation.css
440 ms
jquery.min.js
18 ms
jqModalAndDrag.js
652 ms
WebResource.axd
1066 ms
ScriptResource.axd
1069 ms
ScriptResource.axd
863 ms
ga.js
17 ms
kml3ya1y.Crop.fff.890.390.png
1118 ms
spzc1uxl.Crop.fff.890.390.jpg
1121 ms
ctzzddir.Crop.fff.890.390.jpg
1339 ms
m2o3ihue.Crop.fff.890.390.png
1337 ms
bkgrd.jpg
439 ms
woodstock-logo.png
214 ms
__utm.gif
11 ms
woodstock-logo.png
214 ms
dble-icons.jpg
216 ms
fader-shadow.jpg
428 ms
woodstock.co.nz 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.
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
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
woodstock.co.nz 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
woodstock.co.nz 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Woodstock.co.nz 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 Woodstock.co.nz 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.
woodstock.co.nz
Open Graph description is not detected on the main page of Woodstock. 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: