9.4 sec in total
4 sec
5.2 sec
303 ms
Welcome to teeter.co.nz homepage info - get ready to check Teeter best content right away, or after learning these important things about teeter.co.nz
Inversion therapy for those with back pain.
Visit teeter.co.nzWe analyzed Teeter.co.nz page load time and found that the first response time was 4 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
teeter.co.nz performance score
3971 ms
300 ms
208 ms
213 ms
210 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that all of those requests were addressed to Teeter.co.nz and no external sources were called. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Teeter.co.nz.
Page size can be reduced by 49.0 kB (25%)
195.5 kB
146.5 kB
In fact, the total size of Teeter.co.nz main page is 195.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. 15% of websites need less resources to load. Images take 132.6 kB which makes up the majority of the site volume.
Potential reduce by 17.7 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 17.7 kB or 69% of the original size.
Potential reduce by 256 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. Teeter images are well optimized though.
Potential reduce by 14.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 14.0 kB or 81% of the original size.
Potential reduce by 17.0 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. Teeter.co.nz needs all CSS files to be minified and compressed as it can save up to 17.0 kB or 86% of the original size.
Number of requests can be reduced by 9 (33%)
27
18
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teeter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
teeter.co.nz
3971 ms
style.css
300 ms
listCollapse.js
208 ms
functions.js
213 ms
AC_ActiveX.js
210 ms
AC_RunActiveContent.js
215 ms
bodyBack.jpg
105 ms
pageBack.gif
201 ms
header.gif
206 ms
mainBack.jpg
202 ms
listCircle-ylw2.gif
204 ms
teeterLogo.gif
208 ms
buy-now.jpg
510 ms
graph-staticTest.jpg
500 ms
graph-partsTest.jpg
519 ms
graph-cycleTest.jpg
607 ms
testimonials.gif
417 ms
betterBack.gif
411 ms
shockTheMonkey-ylw.gif
729 ms
inversionGal.jpg
725 ms
inversionGuy.jpg
728 ms
inversionTable.jpg
728 ms
testimonialGuy.jpg
717 ms
circleMonkey.gif
795 ms
monkeys.gif
928 ms
orderButton.gif
928 ms
footer.gif
931 ms
plus.gif
111 ms
teeter.co.nz SEO score
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teeter.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Teeter.co.nz main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
teeter.co.nz
Open Graph description is not detected on the main page of Teeter. 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: