11 sec in total
928 ms
9.8 sec
212 ms
Click here to check amazing Nzweek content. Otherwise, check out these important facts you probably never knew about nzweek.com
NZweek covers every aspect of news and information about New Zealand.
Visit nzweek.comWe analyzed Nzweek.com page load time and found that the first response time was 928 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
nzweek.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.4 s
9/100
25%
Value11.2 s
5/100
10%
Value890 ms
32/100
30%
Value0
100/100
15%
Value6.7 s
56/100
10%
928 ms
141 ms
146 ms
145 ms
146 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 65% of them (43 requests) were addressed to the original Nzweek.com, 11% (7 requests) were made to Pagead2.googlesyndication.com and 8% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Cnzz.mmstat.com.
Page size can be reduced by 194.6 kB (40%)
486.5 kB
291.9 kB
In fact, the total size of Nzweek.com main page is 486.5 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 205.3 kB which makes up the majority of the site volume.
Potential reduce by 42.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. 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 42.5 kB or 80% of the original size.
Potential reduce by 7.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. Nzweek images are well optimized though.
Potential reduce by 121.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 121.7 kB or 61% of the original size.
Potential reduce by 22.6 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. Nzweek.com needs all CSS files to be minified and compressed as it can save up to 22.6 kB or 79% of the original size.
Number of requests can be reduced by 41 (64%)
64
23
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nzweek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.nzweek.com
928 ms
style.css
141 ms
dropdown.css
146 ms
avatars.css
145 ms
imgareaselect.css
146 ms
thickbox.css
147 ms
pagenavi-css.css
207 ms
jquery.js
484 ms
jquery-migrate.min.js
281 ms
tabber-minimized.js
289 ms
dropdown.js
287 ms
jcarousel.js
288 ms
show_ads.js
4 ms
stat.php
1693 ms
jquery.imgareaselect.min.js
278 ms
thickbox.js
358 ms
underscore.min.js
359 ms
shortcode.min.js
359 ms
media-upload.min.js
362 ms
logo.png
203 ms
men_crn_left.png
70 ms
men_crn_right.png
138 ms
men_icon_home.png
137 ms
soc_twitter.png
138 ms
soc_flickr.png
139 ms
soc_rss.png
140 ms
timthumb.php
338 ms
timthumb.php
393 ms
timthumb.php
365 ms
timthumb.php
451 ms
timthumb.php
654 ms
timthumb.php
502 ms
logo_twitter.png
489 ms
ca-pub-3158467778532452.js
134 ms
zrt_lookup.html
36 ms
show_ads_impl.js
63 ms
back_menu.png
487 ms
back_menu_sec.png
524 ms
back_title_blue.png
558 ms
back_title_blue2.png
595 ms
back_title_blue3.png
609 ms
back_title_dark.png
610 ms
back_title_green.png
645 ms
back_title_grey.png
684 ms
back_title_grey2.png
729 ms
back_twitterBox.png
743 ms
ads
240 ms
osd.js
14 ms
ads
242 ms
12566036391510623820
95 ms
abg.js
48 ms
m_js_controller.js
71 ms
googlelogo_color_112x36dp.png
68 ms
13710094253662990065
79 ms
s
29 ms
x_button_blue2.png
33 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
4 ms
stat.htm
167 ms
core.php
1308 ms
activeview
13 ms
9.gif
4112 ms
pic.gif
753 ms
arrows.png
70 ms
loadingAnimation.gif
283 ms
activeview
14 ms
app.gif
1128 ms
nzweek.com accessibility score
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
Links do not have a discernible name
nzweek.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
nzweek.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nzweek.com 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 Nzweek.com 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.
nzweek.com
Open Graph description is not detected on the main page of Nzweek. 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: