Tools & Wizards About Us
womad.co.nz screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

womad.co.nz

WOMAD NZ 14 - 16 March 2025 » WOMAD New Zealand

Page Load Speed

5.5 sec in total

First Response

694 ms

Resources Loaded

4.3 sec

Page Rendered

481 ms

womad.co.nz screenshot

About Website

Click here to check amazing WOMAD content for New Zealand. Otherwise, check out these important facts you probably never knew about womad.co.nz

WOMAD - World of Music, Arts and Dance - the world's festival.

Visit womad.co.nz

Key Findings

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

Performance Metrics

womad.co.nz performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

womad.co.nz

694 ms

www.womad.co.nz

1743 ms

bootstrap.min.css

21 ms

type-ahead-fix.min.css

29 ms

font-awesome.min.css

31 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 39% of them (20 requests) were addressed to the original Womad.co.nz, 55% (28 requests) were made to Cd.womad.co.nz and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Womad.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 300.0 kB (16%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Womad.co.nz main page is 1.8 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 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 26.6 kB

  • Original 34.4 kB
  • After minification 34.3 kB
  • After compression 7.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 26.6 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 142.5 kB

  • Original 1.6 MB
  • After minification 1.5 MB

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. WOMAD images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 24.6 kB

  • Original 51.2 kB
  • After minification 50.8 kB
  • After compression 26.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 24.6 kB or 48% of the original size.

CSS Optimization

-82%

Potential reduce by 106.3 kB

  • Original 130.1 kB
  • After minification 129.8 kB
  • After compression 23.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. Womad.co.nz needs all CSS files to be minified and compressed as it can save up to 106.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (17%)

Requests Now

47

After Optimization

39

  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WOMAD. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

womad.co.nz

womad.co.nz

694 ms

www.womad.co.nz

www.womad.co.nz

1743 ms

bootstrap.min.css

bootstrap.min.css

21 ms

type-ahead-fix.min.css

type-ahead-fix.min.css

29 ms

font-awesome.min.css

font-awesome.min.css

31 ms

stylesheet_combined_bde2eacac1e5133e9300053ce5bad6ad.css

stylesheet_combined_bde2eacac1e5133e9300053ce5bad6ad.css

33 ms

jquery.min.js

jquery.min.js

10 ms

bootstrap.min.js

bootstrap.min.js

84 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

26 ms

twitter-bootstrap-hover-dropdown.min.js

twitter-bootstrap-hover-dropdown.min.js

486 ms

jotform.min.js

jotform.min.js

25 ms

ga.js

ga.js

37 ms

logo2016e.png

logo2016e.png

672 ms

phone_app-2016.jpg

phone_app-2016.jpg

1368 ms

no_gate_sales.jpg

no_gate_sales.jpg

1338 ms

oyster_bar.jpg

oyster_bar.jpg

1117 ms

stageSchedule2016.jpg

stageSchedule2016.jpg

899 ms

follow2016.jpg

follow2016.jpg

1731 ms

view-full-lineup-here2016.jpg

view-full-lineup-here2016.jpg

884 ms

Spotify2016.jpg

Spotify2016.jpg

1111 ms

map.jpg

map.jpg

1799 ms

972-9.jpg

972-9.jpg

1337 ms

freeparking.png

freeparking.png

1338 ms

todd.png

todd.png

1727 ms

tsbbank.png

tsbbank.png

1728 ms

shell.png

shell.png

1728 ms

NPDC.png

NPDC.png

1729 ms

VT.png

VT.png

1781 ms

TSBCT2.png

TSBCT2.png

1782 ms

web-partners2.png

web-partners2.png

1787 ms

bg2016.gif

bg2016.gif

63 ms

bg-bottom2016.jpg

bg-bottom2016.jpg

13 ms

social.png

social.png

12 ms

search.jpg

search.jpg

14 ms

img-883bee6398f2bd1164e1e5da93783bb3.jpg

img-883bee6398f2bd1164e1e5da93783bb3.jpg

14 ms

arrow.png

arrow.png

50 ms

img-20a4fcd550bf9bb99db1653db7d5ed08.jpg

img-20a4fcd550bf9bb99db1653db7d5ed08.jpg

50 ms

img-ebb82112039a6dc350b8ff2e403148ec.jpg

img-ebb82112039a6dc350b8ff2e403148ec.jpg

51 ms

img-3ac9ea714fae314c5ea5386af87df017.jpg

img-3ac9ea714fae314c5ea5386af87df017.jpg

50 ms

img-6e043021abbc06c17cd869570dcb3900.jpg

img-6e043021abbc06c17cd869570dcb3900.jpg

51 ms

img-3d1df9ce1f2c9ee2168333041088630c.jpg

img-3d1df9ce1f2c9ee2168333041088630c.jpg

54 ms

img-7a18d60679ae70e17fd3d363a6b107d9.jpg

img-7a18d60679ae70e17fd3d363a6b107d9.jpg

51 ms

img-1f05b13f62b5d7c6b6a3db2c07c040b3.jpg

img-1f05b13f62b5d7c6b6a3db2c07c040b3.jpg

53 ms

img-64ff1346c75203094aa1befc5d4542f5.jpg

img-64ff1346c75203094aa1befc5d4542f5.jpg

52 ms

img-452012500fcf0b41ea6d76854600e745.jpg

img-452012500fcf0b41ea6d76854600e745.jpg

54 ms

img-87a9c43cd4a9ad8decf37d9557c5c6f0.jpg

img-87a9c43cd4a9ad8decf37d9557c5c6f0.jpg

54 ms

img-780966d42f7351380fbc7b97569c44f1.jpg

img-780966d42f7351380fbc7b97569c44f1.jpg

54 ms

email.jpg

email.jpg

55 ms

__utm.gif

__utm.gif

14 ms

ucb-webfont.woff

ucb-webfont.woff

680 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1385 ms

Accessibility Review

womad.co.nz accessibility score

70

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

womad.co.nz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Page has valid source maps

SEO Factors

womad.co.nz SEO score

92

Search Engine Optimization Advices

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

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

High

Document uses legible font sizes

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 Womad.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 Womad.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

womad.co.nz

Open Graph description is not detected on the main page of WOMAD. 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: