Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

woodstock.co.nz

Woodstock Florist & Design Store, Fresh flowers delivered Wellington

Page Load Speed

5.6 sec in total

First Response

471 ms

Resources Loaded

5 sec

Page Rendered

176 ms

About Website

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. Also stocking Nz made designer gifts & homewares. New Zealand grown fresh cut flowers. Gift wrap bouquets

Visit woodstock.co.nz

Key Findings

We analyzed Woodstock.co.nz page load time and found that the first response time was 471 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

woodstock.co.nz performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.0 s

77/100

10%

Network Requests Diagram

woodstock.co.nz

471 ms

woodstock.co.nz

940 ms

home.aspx

949 ms

modules.css

217 ms

presentation.css

434 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 70% of them (14 requests) were addressed to the original Woodstock.co.nz, 15% (3 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 (2 sec) relates to the external source Images.growonline.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.9 kB (32%)

Content Size

284.9 kB

After Optimization

194.0 kB

In fact, the total size of Woodstock.co.nz main page is 284.9 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.

HTML Optimization

-62%

Potential reduce by 6.1 kB

  • Original 9.9 kB
  • After minification 9.2 kB
  • After compression 3.8 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 6.1 kB or 62% of the original size.

Image Optimization

-32%

Potential reduce by 43.5 kB

  • Original 137.3 kB
  • After minification 93.7 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.

JavaScript Optimization

-21%

Potential reduce by 24.3 kB

  • Original 117.0 kB
  • After minification 108.1 kB
  • After compression 92.7 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.

CSS Optimization

-82%

Potential reduce by 16.9 kB

  • Original 20.7 kB
  • After minification 16.3 kB
  • After compression 3.8 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.

Requests Breakdown

Number of requests can be reduced by 5 (36%)

Requests Now

14

After Optimization

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.

Accessibility Review

woodstock.co.nz accessibility score

56

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

woodstock.co.nz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

woodstock.co.nz SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: