8 sec in total
704 ms
6.8 sec
490 ms
Welcome to trr.co.nz homepage info - get ready to check Trr best content right away, or after learning these important things about trr.co.nz
Want the absolute best rafting experience in Taupo & Turangi? We're #1 on TripAdvisor, with over 230,000 guests. The orginal & still the best.
Visit trr.co.nzWe analyzed Trr.co.nz page load time and found that the first response time was 704 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
trr.co.nz performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value11.0 s
0/100
25%
Value13.8 s
1/100
10%
Value7,280 ms
0/100
30%
Value0.014
100/100
15%
Value17.7 s
4/100
10%
704 ms
2076 ms
60 ms
26 ms
56 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 42% of them (24 requests) were addressed to the original Trr.co.nz, 28% (16 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Trr.co.nz.
Page size can be reduced by 102.1 kB (11%)
905.0 kB
802.8 kB
In fact, the total size of Trr.co.nz main page is 905.0 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. 65% of websites need less resources to load. Images take 626.8 kB which makes up the majority of the site volume.
Potential reduce by 74.1 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. This page needs HTML code to be minified as it can gain 17.0 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 74.1 kB or 82% of the original size.
Potential reduce by 27.2 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. Trr images are well optimized though.
Potential reduce by 178 B
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.
Potential reduce by 692 B
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. Trr.co.nz has all CSS files already compressed.
Number of requests can be reduced by 16 (42%)
38
22
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
trr.co.nz
704 ms
trr.co.nz
2076 ms
gtm.js
60 ms
analytics.js
26 ms
js
56 ms
collect
105 ms
collect
168 ms
wp-emoji-release.min.js
217 ms
ccc70.css
637 ms
css
87 ms
1a603.css
851 ms
1099a.css
676 ms
css
102 ms
79b79.css
696 ms
928dd.js
930 ms
css
99 ms
main.js
109 ms
fe038.js
1406 ms
ga-audiences
45 ms
23240527d5e4987395cd3cfabee4fabc
886 ms
logo.png
797 ms
white-water-rafting-banner5.jpg
1510 ms
300x200-Website-Featured-Image-Whitewater.jpg
1402 ms
blog-arrow.png
794 ms
300x200-Website-Featured-Image-Access-14-2.jpg
1403 ms
IMG_0318-min-e1589151105599-390x250.jpg
794 ms
H2-OHH-4-200x150.jpg
797 ms
river-access-14-6005-200x150.jpg
820 ms
tongario-duo-featured-200x150.jpg
819 ms
white-water-rafting-banner1-150x150.jpg
1400 ms
testimony-image3-150x150.jpg
1399 ms
testimony-image2-150x150.jpg
1400 ms
trr-badge-300x222.png
1457 ms
cca_fern_white-275x300.jpeg
1456 ms
fbevents.js
679 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
999 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
1409 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
1638 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
1638 ms
fontawesome-webfont.woff
862 ms
EYqxmaNOzLlWtsZSScy6XTNs.ttf
1638 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
1637 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
1637 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
1633 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
1808 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
1807 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
1635 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
1808 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
1810 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
1809 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
1826 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
1826 ms
1f449.svg
831 ms
iframe_api
1095 ms
1f448.svg
584 ms
280831755952149
205 ms
www-widgetapi.js
208 ms
trr.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.
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
Links do not have a discernible name
trr.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
trr.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 Trr.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 Trr.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.
trr.co.nz
Open Graph data is detected on the main page of Trr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: