15.2 sec in total
1.3 sec
13.5 sec
313 ms
Welcome to mainlinetrack.co.nz homepage info - get ready to check Mainline Track best content right away, or after learning these important things about mainlinetrack.co.nz
Mainline Track has merged with West-Trak. Stronger together, we now have fresh drive, direction, and focus.
Visit mainlinetrack.co.nzWe analyzed Mainlinetrack.co.nz page load time and found that the first response time was 1.3 sec and then it took 13.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.
mainlinetrack.co.nz performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value145.3 s
0/100
25%
Value42.8 s
0/100
10%
Value4,500 ms
0/100
30%
Value0.133
81/100
15%
Value82.6 s
0/100
10%
1331 ms
81 ms
675 ms
660 ms
665 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 88% of them (66 requests) were addressed to the original Mainlinetrack.co.nz, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (7.4 sec) belongs to the original domain Mainlinetrack.co.nz.
Page size can be reduced by 214.8 kB (43%)
502.4 kB
287.6 kB
In fact, the total size of Mainlinetrack.co.nz main page is 502.4 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. 40% of websites need less resources to load. HTML takes 258.1 kB which makes up the majority of the site volume.
Potential reduce by 213.3 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 213.3 kB or 83% of the original size.
Potential reduce by 494 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. Mainline Track images are well optimized though.
Potential reduce by 1.0 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 65 (93%)
70
5
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mainline Track. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
www.mainlinetrack.co.nz
1331 ms
gtm.js
81 ms
blocks.style.build.css
675 ms
styles.css
660 ms
light-box-styles.css
665 ms
swiper.min.css
672 ms
uaf.css
675 ms
afrfq_front.css
841 ms
font-awesome.css
31 ms
dashicons.min.css
1700 ms
woocommerce-layout.css
1315 ms
woocommerce.css
1528 ms
wpcf7-redirect-frontend.min.css
1314 ms
quadmenu-divi.css
1347 ms
perfect-scrollbar.min.css
1499 ms
owl.carousel.min.css
1957 ms
quadmenu-normalize.css
1968 ms
quadmenu-widgets.css
1997 ms
style.css
2352 ms
quadmenu-locations.css
1765 ms
style.min.css
2338 ms
pum-site-styles.css
2413 ms
style-static.min.css
3036 ms
style.css
2200 ms
jquery.min.js
2855 ms
jquery-migrate.min.js
2853 ms
jquery.blockUI.min.js
3021 ms
add-to-cart.min.js
3001 ms
js.cookie.min.js
3226 ms
woocommerce.min.js
3498 ms
js
90 ms
b4044b3a83146c224b212df.js
391 ms
gravitate_event_tracking.js
3029 ms
wc-blocks.css
3459 ms
facets.css
3663 ms
colors.css
3480 ms
app.build.js
3745 ms
hooks.min.js
3551 ms
i18n.min.js
3537 ms
index.js
3744 ms
api.js
35 ms
index.js
4119 ms
swiper.min.js
3522 ms
afrfq_front.js
3743 ms
wpcf7r-fe.js
3859 ms
scripts.min.js
4300 ms
perfect-scrollbar.jquery.min.js
4126 ms
font-awesome.css
12 ms
owl.carousel.min.js
3583 ms
hoverIntent.min.js
3689 ms
index.js
3534 ms
frontend-bundle.min.js
3721 ms
frontend-bundle.min.js
3689 ms
sourcebuster.min.js
3516 ms
order-attribution.min.js
3798 ms
core.min.js
4049 ms
pum-site-scripts.js
3853 ms
common.js
3727 ms
wp-polyfill.min.js
3919 ms
index.js
3629 ms
smush-lazy-load.min.js
3800 ms
jquery.fitvids.js
3997 ms
css
31 ms
jquery.mobile.js
3640 ms
polyfills.js
3832 ms
facets.js
3808 ms
header-bgr.png
3707 ms
Mainline-Track-Logo-and-Tagline-500.png
3807 ms
Merger-GIF-10s-1.gif
7446 ms
200123023000UniNeueRegular.woff
4189 ms
modules.woff
4292 ms
200116015054UniNeueHeavy.woff
3827 ms
recaptcha__en.js
24 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff
19 ms
woocommerce-smallscreen.css
665 ms
mainlinetrack.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.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
mainlinetrack.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
Page has valid source maps
mainlinetrack.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
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 Mainlinetrack.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 Mainlinetrack.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.
mainlinetrack.co.nz
Open Graph data is detected on the main page of Mainline Track. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: