12.1 sec in total
429 ms
3.1 sec
8.6 sec
Visit pundit.co.nz now to see the best up-to-date Pundit content for New Zealand and also check out these interesting facts you probably never knew about pundit.co.nz
Pundit is an online current affairs and culture blog hub—entirely Kiwi-made—offering you a smart take on what matters in New Zealand and around the world.
Visit pundit.co.nzWe analyzed Pundit.co.nz page load time and found that the first response time was 429 ms and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pundit.co.nz performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value9.0 s
1/100
25%
Value9.2 s
13/100
10%
Value4,100 ms
1/100
30%
Value0.232
54/100
15%
Value17.5 s
4/100
10%
429 ms
136 ms
136 ms
134 ms
137 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 56% of them (45 requests) were addressed to the original Pundit.co.nz, 20% (16 requests) were made to Scoop.co.nz and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (554 ms) relates to the external source Scoop.co.nz.
Page size can be reduced by 432.2 kB (64%)
676.5 kB
244.3 kB
In fact, the total size of Pundit.co.nz main page is 676.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. HTML takes 416.9 kB which makes up the majority of the site volume.
Potential reduce by 320.0 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 320.0 kB or 77% of the original size.
Potential reduce by 672 B
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. Pundit images are well optimized though.
Potential reduce by 77.8 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.8 kB or 50% of the original size.
Potential reduce by 33.8 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. Pundit.co.nz needs all CSS files to be minified and compressed as it can save up to 33.8 kB or 80% of the original size.
Number of requests can be reduced by 44 (55%)
80
36
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pundit. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
pundit.co.nz
429 ms
aggregator.css
136 ms
node.css
136 ms
defaults.css
134 ms
system.css
137 ms
system-menus.css
140 ms
user.css
203 ms
content-module.css
209 ms
nice_menus.css
207 ms
nice_menus_default.css
205 ms
style.css
275 ms
jquery.js
252 ms
drupal.js
267 ms
superfish.js
272 ms
jquery.bgiframe.min.js
273 ms
jquery.hoverIntent.minified.js
288 ms
nice_menus.js
317 ms
googleanalytics.js
332 ms
menu.js
338 ms
scoopad.js
305 ms
v53.js
51 ms
adserve.js
432 ms
analytics.js
17 ms
logonew.gif
71 ms
nar173.gif
72 ms
scoop.jpg
72 ms
publicaddress.jpg
69 ms
kiwiblog.jpg
73 ms
spareroom.jpg
72 ms
picture-23.jpg
141 ms
picture-41.jpg
143 ms
picture-11.jpg
145 ms
picture-10.jpg
144 ms
picture-18604.jpg
142 ms
picture-23717.jpg
145 ms
picture-16847.jpg
213 ms
picture-81.jpg
214 ms
picture-1853.jpg
215 ms
picture-18616.jpg
215 ms
picture-22936.jpg
215 ms
picture-21.jpg
217 ms
picture-1459.jpg
281 ms
picture-18576.jpg
283 ms
picture-24290.jpg
282 ms
picture-22667.jpg
284 ms
poll-of-polls.gif
283 ms
feedicon.png
287 ms
logo-smaller.jpg
349 ms
collect
27 ms
adserve.js
523 ms
adserve.js
312 ms
menubg.gif
243 ms
ga.js
9 ms
__utm.gif
26 ms
textads.css
53 ms
adserve.js
310 ms
adserve.js
348 ms
adserve.js
366 ms
adserve.js
554 ms
adserve.js
552 ms
m
23 ms
serve_creative.html
375 ms
google_service.js
14 ms
serve_creative.html
357 ms
google_ads.js
16 ms
cookie.js
12 ms
ads
40 ms
osd.js
25 ms
__utm.gif
24 ms
adserve.js
298 ms
ads
34 ms
adserve.js
279 ms
serve_creative.html
269 ms
show_ads.js
9 ms
serve_creative.html
294 ms
ca-pub-6735804767414041.js
134 ms
zrt_lookup.html
53 ms
show_ads_impl.js
78 ms
ads
89 ms
osd.js
20 ms
ads
102 ms
pundit.co.nz accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
pundit.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
pundit.co.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Pundit.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 Pundit.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.
pundit.co.nz
Open Graph description is not detected on the main page of Pundit. 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: