Tools & Wizards About Us
ypg.co.nz screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

ypg.co.nz

NZ's Best Wedding Directory and Planning Website & App | My Wedding Guide

Page Load Speed

2.6 sec in total

First Response

45 ms

Resources Loaded

1.4 sec

Page Rendered

1.2 sec

ypg.co.nz screenshot

About Website

Visit ypg.co.nz now to see the best up-to-date Ypg content for New Zealand and also check out these interesting facts you probably never knew about ypg.co.nz

Find everything you need to plan your wedding in New Zealand or Pacific Islands on NZ's most comprehensive wedding website & mobile app My Wedding Guide

Visit ypg.co.nz

Key Findings

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

Performance Metrics

ypg.co.nz performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value3,250 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.479

18/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

ypg.co.nz

45 ms

www.myweddingguide.co.nz

915 ms

58a1b46.css

449 ms

62e64d2.css

29 ms

7c75e3a.css

446 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Ypg.co.nz, 47% (9 requests) were made to Myweddingguide.co.nz and 32% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (915 ms) relates to the external source Myweddingguide.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.8 kB (18%)

Content Size

331.1 kB

After Optimization

271.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ypg.co.nz main page is 331.1 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. 30% of websites need less resources to load. Images take 250.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 59.8 kB

  • Original 76.8 kB
  • After minification 76.8 kB
  • After compression 17.0 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 59.8 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 42 B

  • Original 250.4 kB
  • After minification 250.3 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. Ypg images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 3.9 kB
  • After minification 3.9 kB
  • After compression 3.9 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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

11

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ypg. 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

ypg.co.nz

ypg.co.nz

45 ms

www.myweddingguide.co.nz

www.myweddingguide.co.nz

915 ms

58a1b46.css

58a1b46.css

449 ms

62e64d2.css

62e64d2.css

29 ms

7c75e3a.css

7c75e3a.css

446 ms

hero3.jpg

hero3.jpg

494 ms

css2

css2

31 ms

rocket-loader.min.js

rocket-loader.min.js

5 ms

main.js

main.js

9 ms

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWUBw.ttf

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWUBw.ttf

17 ms

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhycKUBw.ttf

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhycKUBw.ttf

25 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4VrMPrQ.ttf

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4VrMPrQ.ttf

40 ms

6xKhdSpbNNCT-vWI.ttf

6xKhdSpbNNCT-vWI.ttf

45 ms

jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oZ8RNDM.ttf

jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oZ8RNDM.ttf

80 ms

jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oabQ9DM.ttf

jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oabQ9DM.ttf

73 ms

gtm.js

gtm.js

56 ms

a449be6.js

a449be6.js

13 ms

41f738c.js

41f738c.js

16 ms

6d59149.js

6d59149.js

37 ms

Accessibility Review

ypg.co.nz accessibility score

83

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ypg.co.nz SEO score

81

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ypg.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ypg.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

ypg.co.nz

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