Tools & Wizards About Us
princes-wharf.co.nz screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

princes-wharf.co.nz

Princes Wharf Auckland - Official Website

Page Load Speed

5.6 sec in total

First Response

1.1 sec

Resources Loaded

4.2 sec

Page Rendered

256 ms

princes-wharf.co.nz screenshot

About Website

Click here to check amazing Princes Wharf content. Otherwise, check out these important facts you probably never knew about princes-wharf.co.nz

Looking out on the stunning Waitemata Harbour, Princes Wharf is home to a mixture of bars and restaurants as well as the five star Hilton Auckland all in the Heart of the City. View all upcoming event...

Visit princes-wharf.co.nz

Key Findings

We analyzed Princes-wharf.co.nz page load time and found that the first response time was 1.1 sec and then it took 4.5 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

princes-wharf.co.nz performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

princes-wharf.co.nz

1070 ms

wp-emoji-release.min.js

16 ms

ie.css

474 ms

style.dev.css

875 ms

style.css

48 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 76% of them (56 requests) were addressed to the original Princes-wharf.co.nz, 7% (5 requests) were made to Use.typekit.net and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Princes-wharf.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.7 kB (10%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 33.4 kB

  • Original 42.6 kB
  • After minification 39.2 kB
  • After compression 9.3 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 33.4 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 691 B

  • Original 1.4 MB
  • After minification 1.4 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. Princes Wharf images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 143.1 kB

  • Original 440.8 kB
  • After minification 440.6 kB
  • After compression 297.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 143.1 kB or 32% of the original size.

CSS Optimization

-9%

Potential reduce by 16.6 kB

  • Original 178.0 kB
  • After minification 177.3 kB
  • After compression 161.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. Princes-wharf.co.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (78%)

Requests Now

67

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

princes-wharf.co.nz

princes-wharf.co.nz

1070 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

16 ms

ie.css

ie.css

474 ms

style.dev.css

style.dev.css

875 ms

style.css

style.css

48 ms

style.css

style.css

52 ms

css

css

57 ms

eventon_styles.css

eventon_styles.css

47 ms

font-awesome.css

font-awesome.css

45 ms

eventon_dynamic_styles.css

eventon_dynamic_styles.css

63 ms

css

css

72 ms

shortcodes_responsive.css

shortcodes_responsive.css

64 ms

magnific_popup.css

magnific_popup.css

59 ms

formreset.min.css

formreset.min.css

60 ms

formsmain.min.css

formsmain.min.css

67 ms

readyclass.min.css

readyclass.min.css

72 ms

browsers.min.css

browsers.min.css

73 ms

dashicons.min.css

dashicons.min.css

74 ms

wpmu-ui.3.min.css

wpmu-ui.3.min.css

77 ms

animate.3.min.css

animate.3.min.css

78 ms

jquery.js

jquery.js

81 ms

jquery-migrate.min.js

jquery-migrate.min.js

83 ms

wpgmza_data.js

wpgmza_data.js

87 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

90 ms

recaptcha.js

recaptcha.js

90 ms

jquery.json.min.js

jquery.json.min.js

94 ms

gravityforms.min.js

gravityforms.min.js

95 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

98 ms

sdk8zvt.css

sdk8zvt.css

192 ms

css

css

63 ms

js

js

92 ms

et-core-unified-18-17086395179955.min.css

et-core-unified-18-17086395179955.min.css

98 ms

email-decode.min.js

email-decode.min.js

96 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

105 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

106 ms

custom.js

custom.js

105 ms

eventon_functions.js

eventon_functions.js

107 ms

handlebars.js

handlebars.js

113 ms

jquery.mobile.min.js

jquery.mobile.min.js

117 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

113 ms

eventon_script.js

eventon_script.js

116 ms

js

js

80 ms

jquery.fitvids.js

jquery.fitvids.js

126 ms

waypoints.min.js

waypoints.min.js

116 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

88 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

89 ms

common.js

common.js

89 ms

wpmu-ui.3.min.js

wpmu-ui.3.min.js

91 ms

public.min.js

public.min.js

83 ms

wp-embed.min.js

wp-embed.min.js

89 ms

eventon_gen_maps.js

eventon_gen_maps.js

90 ms

eventon_init_gmap.js

eventon_init_gmap.js

87 ms

p.css

p.css

30 ms

js

js

57 ms

analytics.js

analytics.js

53 ms

new-princes-wharf-logo2-1.png

new-princes-wharf-logo2-1.png

50 ms

home-banner-new.jpg

home-banner-new.jpg

205 ms

temp-banner2.jpg

temp-banner2.jpg

1507 ms

temp-banner3.jpg

temp-banner3.jpg

205 ms

icon-eat.png

icon-eat.png

39 ms

icon-drink.png

icon-drink.png

203 ms

icon-stay.png

icon-stay.png

203 ms

footer2.jpg

footer2.jpg

205 ms

font

font

191 ms

font

font

192 ms

font

font

207 ms

d

d

172 ms

evo_fontawesome-webfont.woff

evo_fontawesome-webfont.woff

1002 ms

font

font

206 ms

d

d

175 ms

d

d

231 ms

d

d

175 ms

modules.ttf

modules.ttf

1028 ms

collect

collect

141 ms

Accessibility Review

princes-wharf.co.nz accessibility score

88

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

princes-wharf.co.nz best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

princes-wharf.co.nz SEO score

89

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

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

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 Princes-wharf.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 Princes-wharf.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

princes-wharf.co.nz

Open Graph data is detected on the main page of Princes Wharf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: