18.3 sec in total
5.5 sec
12.6 sec
237 ms
Welcome to whitestonetaxis.co.nz homepage info - get ready to check Whitestonetaxis best content right away, or after learning these important things about whitestonetaxis.co.nz
Just another WordPress site
Visit whitestonetaxis.co.nzWe analyzed Whitestonetaxis.co.nz page load time and found that the first response time was 5.5 sec and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
whitestonetaxis.co.nz performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.8 s
30/100
25%
Value7.2 s
30/100
10%
Value0 ms
100/100
30%
Value0.145
77/100
15%
Value4.5 s
82/100
10%
5465 ms
480 ms
479 ms
719 ms
799 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 97% of them (61 requests) were addressed to the original Whitestonetaxis.co.nz, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Whitestonetaxis.co.nz.
Page size can be reduced by 405.3 kB (26%)
1.6 MB
1.2 MB
In fact, the total size of Whitestonetaxis.co.nz main page is 1.6 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 19.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 19.2 kB or 78% of the original size.
Potential reduce by 11.1 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. Whitestonetaxis images are well optimized though.
Potential reduce by 254.1 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 254.1 kB or 71% of the original size.
Potential reduce by 120.9 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. Whitestonetaxis.co.nz needs all CSS files to be minified and compressed as it can save up to 120.9 kB or 72% of the original size.
Number of requests can be reduced by 33 (59%)
56
23
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whitestonetaxis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
whitestonetaxis.co.nz
5465 ms
style.css
480 ms
style.css
479 ms
dashicons.min.css
719 ms
desktop_style.css
799 ms
settings.css
805 ms
prettyPhoto.css
722 ms
fullwidth.css
720 ms
colorpicker.css
718 ms
jquery.js
1282 ms
jquery-migrate.min.js
1230 ms
front_end_script.js
1238 ms
jquery.themepunch.plugins.min.js
1319 ms
jquery.themepunch.revolution.min.js
1033 ms
wp-embed.min.js
3175 ms
jquery.easing.1.3.js
1047 ms
superfish.js
1243 ms
supersubs.js
1250 ms
jquery.prettyPhoto.js
1284 ms
mobilenav.js
1293 ms
custom.js
1330 ms
forms.js
1480 ms
jquery.carouFredSel-5.5.0-packed.js
1495 ms
jquery.flexslider.js
1522 ms
reset.css
1288 ms
skeleton.css
1326 ms
superfish.css
1526 ms
flexslider.css
1528 ms
wp-emoji-release.min.js
2391 ms
analytics.js
20 ms
01.jpg
241 ms
People-Papers-Parcels-Post1.jpg
479 ms
van1.jpg
1438 ms
prius1.jpg
1433 ms
whitestone-Taxis_saloon.jpg
5000 ms
back-top.png
956 ms
rss.png
1196 ms
02_tumb.jpg
1437 ms
03_tumb.jpg
1672 ms
04_tumb.jpg
1712 ms
05_tumb.jpg
1678 ms
06_tumb.jpg
1917 ms
07_tumb.jpg
2022 ms
08_tumb.jpg
1937 ms
09_tumb.jpg
1949 ms
01_tumb.jpg
2156 ms
bg_tagline.png
2165 ms
shadow.png
2177 ms
bullets.png
2250 ms
dotted.png
2384 ms
footer_overlay.png
3358 ms
opensans-regular-webfont.woff
2416 ms
aller_lt-webfont.woff
2486 ms
collect
14 ms
museo_slab_500-webfont.woff
2599 ms
aller_bd-webfont.woff
2633 ms
timer.png
1406 ms
loader.gif
1578 ms
shadow2.png
1927 ms
small_left.png
241 ms
small_right.png
241 ms
large_left.png
244 ms
large_right.png
241 ms
whitestonetaxis.co.nz 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
Document doesn't have a <title> element
whitestonetaxis.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
whitestonetaxis.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
Document doesn't have a <title> element
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 Whitestonetaxis.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 Whitestonetaxis.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.
whitestonetaxis.co.nz
Open Graph data is detected on the main page of Whitestonetaxis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: