Tools & Wizards About Us
ypg.co.nz screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ypg.co.nz

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

Page Load Speed

4.9 sec in total

First Response

606 ms

Resources Loaded

4.1 sec

Page Rendered

224 ms

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 606 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

ypg.co.nz performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value5,390 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.369

29/100

15%

TTI (Time to Interactive)

Value27.8 s

0/100

10%

Network Requests Diagram

ypg.co.nz

606 ms

www.ypg.co.nz

765 ms

960.css

194 ms

jquery.fancybox-1.3.4.css

390 ms

style.css

578 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 72% of them (36 requests) were addressed to the original Ypg.co.nz, 22% (11 requests) were made to Header.yellow.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.6 sec) belongs to the original domain Ypg.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.4 kB (43%)

Content Size

807.1 kB

After Optimization

457.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 61.6 kB

  • Original 72.8 kB
  • After minification 67.4 kB
  • After compression 11.2 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 61.6 kB or 85% of the original size.

Image Optimization

-25%

Potential reduce by 132.6 kB

  • Original 529.3 kB
  • After minification 396.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, Ypg needs image optimization as it can save up to 132.6 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 77.4 kB

  • Original 114.6 kB
  • After minification 107.9 kB
  • After compression 37.2 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 77.4 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 77.9 kB

  • Original 90.4 kB
  • After minification 60.0 kB
  • After compression 12.5 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. Ypg.co.nz needs all CSS files to be minified and compressed as it can save up to 77.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (41%)

Requests Now

44

After Optimization

26

  • Images
  • JavaScript
  • CSS

The browser has sent 44 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 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ypg.co.nz

ypg.co.nz

606 ms

www.ypg.co.nz

www.ypg.co.nz

765 ms

960.css

960.css

194 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

390 ms

style.css

style.css

578 ms

extra.css

extra.css

385 ms

selectivizr-min.js

selectivizr-min.js

395 ms

jquery.min.js

jquery.min.js

9 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

670 ms

script.js

script.js

454 ms

extra.js

extra.js

628 ms

yellowheader.js

yellowheader.js

629 ms

bg-submenu.png

bg-submenu.png

193 ms

btn-self.png

btn-self.png

193 ms

btn-yellow-bill.png

btn-yellow-bill.png

764 ms

btn-search-small.png

btn-search-small.png

228 ms

bg-menu.gif

bg-menu.gif

196 ms

bg-menu-curve.gif

bg-menu-curve.gif

305 ms

bg-submenu-active.png

bg-submenu-active.png

383 ms

btn-ss-prev.png

btn-ss-prev.png

384 ms

btn-ss-next.png

btn-ss-next.png

390 ms

New_Yellow.co.png

New_Yellow.co.png

1582 ms

__bg2_1.jpg

__bg2_1.jpg

1418 ms

sidebar-top-grey.png

sidebar-top-grey.png

574 ms

yellow_book.png

yellow_book.png

577 ms

bus-knowhow_115_80.png

bus-knowhow_115_80.png

1161 ms

more_stats.jpg

more_stats.jpg

960 ms

module-teaser-top-orange.png

module-teaser-top-orange.png

770 ms

recycle_logoteaser.jpg

recycle_logoteaser.jpg

953 ms

module-teaser-top-yellow.png

module-teaser-top-yellow.png

963 ms

module-teaser-top-blue.png

module-teaser-top-blue.png

1145 ms

Yellowbusinesslogo.jpg

Yellowbusinesslogo.jpg

1153 ms

module-teaser-top-purple.png

module-teaser-top-purple.png

1154 ms

tile_digitalsolutions.jpg

tile_digitalsolutions.jpg

1532 ms

ga.js

ga.js

21 ms

header.php

header.php

792 ms

icon-ss-inactive.png

icon-ss-inactive.png

1250 ms

bg-trans-green.png

bg-trans-green.png

1249 ms

icon-ss-active.png

icon-ss-active.png

1256 ms

select_skin.png

select_skin.png

1439 ms

__utm.gif

__utm.gif

12 ms

yolLogo.svg

yolLogo.svg

199 ms

footer.css

footer.css

385 ms

appLogoAppleAppstore.svg

appLogoAppleAppstore.svg

766 ms

appLogoGooglePlay.svg

appLogoGooglePlay.svg

580 ms

yellow-windows-store1.svg

yellow-windows-store1.svg

594 ms

roboto-light-webfont.woff

roboto-light-webfont.woff

882 ms

roboto-regular-webfont.woff

roboto-regular-webfont.woff

205 ms

roboto-bold-webfont.woff

roboto-bold-webfont.woff

671 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

752 ms

Accessibility Review

ypg.co.nz accessibility score

75

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

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

ypg.co.nz best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ypg.co.nz SEO score

79

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    ISO-8859-1

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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ypg.co.nz main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

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: