Tools & Wizards About Us
pwc.co.nz screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pwc.co.nz

PwC New Zealand

Page Load Speed

6 sec in total

First Response

1.3 sec

Resources Loaded

4.6 sec

Page Rendered

139 ms

pwc.co.nz screenshot

About Website

Welcome to pwc.co.nz homepage info - get ready to check PwC best content for New Zealand right away, or after learning these important things about pwc.co.nz

PwC New Zealand employs over 1,600 people and has offices in the Auckland, Waikato, Hawkes Bay, Wellington, Canterbury and Otago regions. Our people are dedicated to solving the complex problems busin...

Visit pwc.co.nz

Key Findings

We analyzed Pwc.co.nz page load time and found that the first response time was 1.3 sec 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. This domain responded with an error, which can significantly jeopardize Pwc.co.nz rating and web reputation

Performance Metrics

pwc.co.nz performance score

0

Network Requests Diagram

www.pwc.co.nz

1251 ms

GetResource.ashx

379 ms

GetResource.ashx

388 ms

GetResource.ashx

592 ms

nz.js

634 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 86% of them (43 requests) were addressed to the original Pwc.co.nz, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Download.pwc.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Pwc.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 522.5 kB (34%)

Content Size

1.5 MB

After Optimization

993.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 101.8 kB

  • Original 132.4 kB
  • After minification 118.5 kB
  • After compression 30.5 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. This page needs HTML code to be minified as it can gain 13.9 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 101.8 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 94.4 kB

  • Original 918.3 kB
  • After minification 823.9 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. PwC images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 265.6 kB

  • Original 392.9 kB
  • After minification 355.2 kB
  • After compression 127.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 265.6 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 60.6 kB

  • Original 72.0 kB
  • After minification 52.7 kB
  • After compression 11.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. Pwc.co.nz needs all CSS files to be minified and compressed as it can save up to 60.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (70%)

Requests Now

47

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PwC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.pwc.co.nz

www.pwc.co.nz

1251 ms

GetResource.ashx

GetResource.ashx

379 ms

GetResource.ashx

GetResource.ashx

388 ms

GetResource.ashx

GetResource.ashx

592 ms

nz.js

nz.js

634 ms

WebResource.axd

WebResource.axd

193 ms

ScriptResource.axd

ScriptResource.axd

573 ms

ScriptResource.axd

ScriptResource.axd

401 ms

jquery1.8.3.min.js

jquery1.8.3.min.js

1133 ms

underscore.min.js

underscore.min.js

567 ms

intention.js

intention.js

388 ms

context.js

context.js

426 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

605 ms

jquery.reveal.js

jquery.reveal.js

605 ms

lazyload.js

lazyload.js

629 ms

nav.js

nav.js

756 ms

main.js

main.js

759 ms

pwc-twitter-widget-1.0.css

pwc-twitter-widget-1.0.css

762 ms

pwc-twitter-widget-1.0.js

pwc-twitter-widget-1.0.js

787 ms

wtid.js

wtid.js

21 ms

pwclogo.gif

pwclogo.gif

515 ms

m-menu-32.gif

m-menu-32.gif

647 ms

searchsubmit.gif

searchsubmit.gif

650 ms

icon_close.gif

icon_close.gif

653 ms

Optimals4-25-V2-244x419.png

Optimals4-25-V2-244x419.png

1260 ms

pwc-herald-talks-195x90.jpg

pwc-herald-talks-195x90.jpg

918 ms

adding-value-244x419.jpg

adding-value-244x419.jpg

1028 ms

homefollow-facebook.gif

homefollow-facebook.gif

915 ms

homefollow-twitter.gif

homefollow-twitter.gif

916 ms

homefollow-linkedin.gif

homefollow-linkedin.gif

1022 ms

homefollow-google.gif

homefollow-google.gif

1029 ms

homefollow-youtube.gif

homefollow-youtube.gif

1033 ms

visit-our-apps-page-to-download-pwc-apps-2014.jpg

visit-our-apps-page-to-download-pwc-apps-2014.jpg

1892 ms

gtm.js

gtm.js

71 ms

analytics.js

analytics.js

16 ms

collect

collect

23 ms

collect

collect

61 ms

tangerine_arrow_down.gif

tangerine_arrow_down.gif

907 ms

sprites.gif

sprites.gif

919 ms

services-arrow.gif

services-arrow.gif

918 ms

arrow-left.jpg

arrow-left.jpg

329 ms

arrow-right.jpg

arrow-right.jpg

503 ms

homeslider-left.gif

homeslider-left.gif

514 ms

homeslider-right.gif

homeslider-right.gif

516 ms

data

data

104 ms

pwc-new-zealands-cyber-security-strategy-adrian-van-hest-192x105.jpg

pwc-new-zealands-cyber-security-strategy-adrian-van-hest-192x105.jpg

501 ms

ajaxload.gif

ajaxload.gif

540 ms

pwc-eugen-trombitas-on-gst-law-reform-on-offshore-online-purchases-192x105.jpg

pwc-eugen-trombitas-on-gst-law-reform-on-offshore-online-purchases-192x105.jpg

507 ms

nz-ceo-survey-2016-homepage-banner-980x419-with-stat-2.jpg

nz-ceo-survey-2016-homepage-banner-980x419-with-stat-2.jpg

1446 ms

pwc-global-economic-crime-survey-2016-nz-insights-490x419.jpg

pwc-global-economic-crime-survey-2016-nz-insights-490x419.jpg

892 ms

SEO Factors

pwc.co.nz SEO score

0

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

pwc.co.nz

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