4.6 sec in total
56 ms
4.2 sec
431 ms
Welcome to notices.nzherald.co.nz homepage info - get ready to check Notices Nz Herald best content for New Zealand right away, or after learning these important things about notices.nzherald.co.nz
The New Zealand Herald notices and Death Notices for Auckland Auckland area . Explore Life Stories, Offer Condolences & Send Flowers.
Visit notices.nzherald.co.nzWe analyzed Notices.nzherald.co.nz page load time and found that the first response time was 56 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
notices.nzherald.co.nz performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value24.1 s
0/100
25%
Value17.8 s
0/100
10%
Value5,800 ms
0/100
30%
Value0.099
90/100
15%
Value35.5 s
0/100
10%
56 ms
71 ms
124 ms
70 ms
96 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Notices.nzherald.co.nz, 22% (24 requests) were made to Www2.nzherald.co.nz and 16% (18 requests) were made to Static.legacy.net. The less responsive or slowest element that took the longest time to load (893 ms) relates to the external source Media.nzherald.co.nz.
Page size can be reduced by 408.7 kB (32%)
1.3 MB
856.0 kB
In fact, the total size of Notices.nzherald.co.nz main page is 1.3 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. 70% of websites need less resources to load. Javascripts take 666.3 kB which makes up the majority of the site volume.
Potential reduce by 247.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 247.2 kB or 84% of the original size.
Potential reduce by 20.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, Notices Nz Herald needs image optimization as it can save up to 20.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 136.5 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 136.5 kB or 20% of the original size.
Potential reduce by 4.3 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. Notices.nzherald.co.nz has all CSS files already compressed.
Number of requests can be reduced by 56 (60%)
94
38
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Notices Nz Herald. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
56 ms
components.css
71 ms
asrsecure.css
124 ms
css
70 ms
css
96 ms
jquery.min.js
91 ms
jquery.unveil.js
123 ms
jquery.loading.js
116 ms
responsive-obituaries-portal.js
158 ms
responsive-main.js
156 ms
gpt.js
183 ms
10698.js
157 ms
ClientStorage.ascx.js
119 ms
ObituaryNavigator.js
153 ms
jquery-ui-custom.js
183 ms
outdatedbrowser.js
199 ms
PaspHeader.ascx.js
180 ms
LocalSpotlight.ascx.js
197 ms
RecentObituariesV2.ascx.js
180 ms
SearchObitContent.ascx.js
199 ms
ResourceModule.ascx.js
240 ms
Custom11x5Ad.ascx.js
242 ms
obituary-portal-content3.aspx.js
240 ms
pl.ashx
58 ms
v52.js
84 ms
react.production.min.js
83 ms
react-dom.production.min.js
99 ms
components.bundle.js
77 ms
css
46 ms
css
48 ms
v52.js
61 ms
background1000.gif
893 ms
gpt.js
225 ms
v2nlfZdn3WoydGB1vjUETH1FnPIs9s3tfOmWUoMQxerMX82X2Uytr4JrrHDfUxs_v
376 ms
apstag.js
360 ms
gtm.js
415 ms
sdk.js
195 ms
ClientStorageProxy.aspx
128 ms
affiliateartwork.axd
239 ms
photo_032633_12292289_1_20240628.jpgx
470 ms
bg_tile.gif
118 ms
photo_032633_12292290_1_20240628.jpgx
469 ms
photo_032633_12291806_1_20240628.jpgx
464 ms
photo_032633_12292744_1_20240628.jpgx
493 ms
photo_032633_12292182_1_20240628.jpgx
468 ms
photo_032633_12290930_1_20240628.jpgx
468 ms
photo_032633_12291852_1_20240628.jpgx
548 ms
photo_032633_12292752_1_20240628.jpgx
568 ms
nzherald-nz.gif
568 ms
obit_preview.png
492 ms
pubads_impl.js
167 ms
bg_tile.gif
115 ms
wlp2gwHKFkZgtmSR3NB0oRJfbwhV.woff
340 ms
wlppgwHKFkZgtmSR3NB0oRJXsCxGDNNW.woff
355 ms
wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNW.woff
382 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
382 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
382 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
370 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
382 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff
357 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexg.woff
367 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexg.woff
368 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff
367 ms
ClickBoothAd.axd
279 ms
optimizationscripts.js
99 ms
affiliateartwork.axd
306 ms
match
315 ms
storageframe.html
203 ms
sdk.js
195 ms
jquery.min.js
143 ms
423686928
170 ms
nzh_header.cfm
848 ms
110 ms
display_ads.php
44 ms
nzh_footer.cfm
771 ms
config250.js
31 ms
nlsSDK600.bundle.min.js
17 ms
ls.html
29 ms
gn
31 ms
package.css
340 ms
master.js
736 ms
nzhPackage-head-min.js
382 ms
nzhdata.js
767 ms
v60.js
2 ms
nzhPackage-foot-min.js
830 ms
v60.js
3 ms
gtm.js
69 ms
package.css
785 ms
nzhPackage-head-min.js
676 ms
nzhPackage-foot-min.js
695 ms
email-decode.min.js
682 ms
footerSprite.png
323 ms
iconSprite.png
320 ms
match
64 ms
navigation.html
326 ms
StagWeb-Medium.woff
363 ms
StagSansWeb-Medium.woff
398 ms
Headfoot-sprites.png
355 ms
weatherSpriteSmall.png
509 ms
mainSprite.png
452 ms
celebration-bg-image.jpg
647 ms
match
61 ms
bookNoticeSprite.png
548 ms
header_promotile.html
534 ms
gn
12 ms
gn
3 ms
iconSprite.png
369 ms
StagWeb-Book.woff
493 ms
nightchoir_300x50.gif
732 ms
pl.js
57 ms
notices.nzherald.co.nz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
notices.nzherald.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
notices.nzherald.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Notices.nzherald.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 Notices.nzherald.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.
notices.nzherald.co.nz
Open Graph data is detected on the main page of Notices Nz Herald. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: