13.6 sec in total
2.1 sec
7 sec
4.6 sec
Welcome to transportblog.co.nz homepage info - get ready to check Transport Blog best content for New Zealand right away, or after learning these important things about transportblog.co.nz
All about Auckland's public transport. Read about the possible solutions to the worsening traffic and congestion in Auckland.
Visit transportblog.co.nzWe analyzed Transportblog.co.nz page load time and found that the first response time was 2.1 sec and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
transportblog.co.nz performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value4.0 s
51/100
25%
Value5.6 s
53/100
10%
Value230 ms
86/100
30%
Value0.023
100/100
15%
Value5.4 s
72/100
10%
2060 ms
379 ms
404 ms
589 ms
404 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 39% of them (55 requests) were addressed to the original Transportblog.co.nz, 17% (24 requests) were made to Pbs.twimg.com and 7% (10 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Transportblog.co.nz.
Page size can be reduced by 1.1 MB (20%)
5.7 MB
4.5 MB
In fact, the total size of Transportblog.co.nz main page is 5.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 153.4 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 153.4 kB or 77% of the original size.
Potential reduce by 357.4 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. Transport Blog images are well optimized though.
Potential reduce by 311.6 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 311.6 kB or 63% of the original size.
Potential reduce by 316.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. Transportblog.co.nz needs all CSS files to be minified and compressed as it can save up to 316.5 kB or 75% of the original size.
Number of requests can be reduced by 56 (41%)
137
81
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Transport Blog. 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 14 to 1 for CSS and as a result speed up the page load time.
transportblog.co.nz
2060 ms
tb.css
379 ms
style.css
404 ms
dashicons.min.css
589 ms
desktop_style.css
404 ms
polls-css.css
404 ms
default.min.css
511 ms
genericons.css
753 ms
jetpack.css
581 ms
jquery.js
828 ms
jquery-migrate.min.js
590 ms
front_end_script.js
701 ms
DD_roundies.js
772 ms
Chart.min.js
776 ms
jquery.colorbox.min.js
787 ms
widgets.js
85 ms
e-201609.js
4 ms
wp-emoji-release.min.js
501 ms
blogheader.gif
1329 ms
expand-down.gif
1318 ms
inputbackgr.gif
1318 ms
magnifier2-gray.gif
1318 ms
web2.jpg
1330 ms
1929-Morningside-Deviation-K-Rd-station.jpg
2511 ms
auckland1946-plan.jpg
2186 ms
railwaydevelopmentscheme.jpg
2262 ms
rail-spur.jpg
1703 ms
spur-map.jpg
1833 ms
De-Leuw-Cather-Rapid-Transit.jpg
2381 ms
downtown-map.jpg
2185 ms
queen-customs-station-design.jpg
1918 ms
1970-Proposed-Rapid-Transit-Network.jpg
2879 ms
IMG_0615.jpg
2776 ms
IMG_0608.jpg
2765 ms
1974-4.jpg
2825 ms
2004-study-urs1.jpg
2772 ms
downtown-tracks.jpg
2701 ms
routeoptions.jpg
3084 ms
CRL-Route.jpg
3731 ms
Auckland-Urban-Growth.jpg
3163 ms
Orakei-Sections-2.gif
3754 ms
AKL-consents-1024x669.png
3762 ms
Chch-consents-1024x669.png
3648 ms
MfE-nz-2020-emissions-target-vs-projections.gif
3276 ms
eight_col_PCE_report-map-DUN.jpg
3556 ms
Annual-CO2-emissions-per-commuter-v1-1024x724.jpg
3850 ms
definition-of-high-rise.jpg
3951 ms
upzoning-map.jpg
4032 ms
ACDC-model-output.jpg
3924 ms
feasible-capacity.jpg
3953 ms
atap-jobs-accessibility.jpg
3948 ms
TFUG-Potential-Network-Dairy-Flat-Millwater.jpg
4231 ms
TFUG-Potential-Network-Warkworth.jpg
4115 ms
sdk.js
119 ms
WeeklyWellwornHoatzin
1285 ms
ministers-submission.jpg
4058 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
15 ms
1XUEvkMZHno
1251 ms
GFAN.min.js
1208 ms
clipboard.min.js
1175 ms
lDPN0VQVDY8
1297 ms
1286 ms
xd_arbiter.php
1243 ms
xd_arbiter.php
1341 ms
analytics.js
1160 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
216 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
257 ms
tweet.04d20138f67ab41d6b4af6cc583926d9.js
331 ms
g.gif
37 ms
Genericons.svg
2837 ms
ministers-relief.jpg
3032 ms
HNZ-Intensification-figures-vs-Council.jpg
2913 ms
sharing-facebook.svg
54 ms
sharing-twitter.svg
72 ms
sharing-tumblr.svg
95 ms
sharing-reddit.svg
101 ms
sharing-pinterest.svg
135 ms
collect
48 ms
pix.gif
142 ms
analytics.js
119 ms
atrk.js
109 ms
gfycat_logo.svg
69 ms
www-embed-player-vflZsBgOl.css
138 ms
www-embed-player.js
203 ms
base.js
309 ms
quant.js
97 ms
pix.gif
125 ms
collect
114 ms
page.php
171 ms
atrk.gif
45 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
62 ms
pixel;r=1409176366;a=p-JLXEY2nbGDmpc;fpan=1;fpa=P0-1767095171-1456786810579;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456786810578;tzo=-180;ref=http%3A%2F%2Ftransportblog.co.nz%2F;url=https%3A%2F%2Fgfycat.com%2Fifr%2FWeeklyWellwornHoatzin;ogl=
138 ms
syndication
277 ms
346360605575356417
283 ms
PGVGVQG1jIH.css
239 ms
_rx8naC75Dy.js
263 ms
t-KLv3gqZy0.js
289 ms
uLtKx7ldlvR.js
324 ms
tweets.json
246 ms
syndication
199 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
238 ms
ad_status.js
144 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
250 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
340 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
67 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
151 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
123 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
177 ms
563688_497816120265735_671491692_n.jpg
314 ms
10450934_887127238001286_565171290655156444_n.jpg
333 ms
wL6VQj7Ab77.png
148 ms
CSXXCvknpgK.png
148 ms
33d20674468261e5516d6f55fa50f941_normal.jpeg
194 ms
FI7T54E8_normal.jpg
181 ms
Rj1Kv4PN_normal.jpeg
179 ms
d96803a3d1ecd04a3a34185440b8a4fa_normal.jpeg
179 ms
dO6ObCYI_normal.png
183 ms
A5ubtfwm_normal.jpg
184 ms
rtxGC1P6_normal.jpeg
186 ms
46nRq04N_normal.jpeg
186 ms
CcaejfgUkAE-NtR.jpg:small
188 ms
CcZo-1TUUAMJIcj.jpg:small
189 ms
CcXfCecUUAAnufc.jpg:small
197 ms
CcXdV3CWEAIjQi1.jpg:small
195 ms
4iKwvC9V_normal.jpeg
157 ms
LAMiWt6D_normal.jpg
156 ms
knKr__l__normal.jpg
156 ms
sacha_normal.png
155 ms
iq8z0O5N_normal.jpeg
159 ms
CbQJBAeW0AAhNMP.jpg:large
162 ms
17_4IjI-_normal.jpg
160 ms
GKGP1-VA_normal.jpg
158 ms
hpLyUknh_normal.jpg
160 ms
Zrah0Igz_normal.png
160 ms
CcB7XCJUMAEBAw2.png:small
178 ms
FGaVbAbZ_normal.png
162 ms
R9a_DtVRZgv.js
18 ms
cUDgRFxaoIk.js
25 ms
0JBr1QHp8Gi.js
19 ms
kDOzhTr2W91.js
34 ms
jot.html
31 ms
collect
10 ms
transportblog.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
transportblog.co.nz 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
transportblog.co.nz SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Transportblog.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 Transportblog.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.
transportblog.co.nz
Open Graph description is not detected on the main page of Transport Blog. 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: