6.8 sec in total
599 ms
6 sec
214 ms
Visit teapea.co.nz now to see the best up-to-date Tea Pea content for New Zealand and also check out these interesting facts you probably never knew about teapea.co.nz
Find something truly unique and special at our gift store in Wellington. Browse boutique stationery, homewares and more.
Visit teapea.co.nzWe analyzed Teapea.co.nz page load time and found that the first response time was 599 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
teapea.co.nz performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value14.3 s
0/100
25%
Value7.8 s
24/100
10%
Value1,490 ms
14/100
30%
Value0.141
78/100
15%
Value20.1 s
2/100
10%
599 ms
232 ms
26 ms
456 ms
460 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 93% of them (38 requests) were addressed to the original Teapea.co.nz, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Teapea.co.nz.
Page size can be reduced by 174.7 kB (68%)
255.8 kB
81.0 kB
In fact, the total size of Teapea.co.nz main page is 255.8 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. Javascripts take 155.5 kB which makes up the majority of the site volume.
Potential reduce by 13.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 13.3 kB or 79% of the original size.
Potential reduce by 1.5 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. Obviously, Tea Pea needs image optimization as it can save up to 1.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 98.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 98.6 kB or 63% of the original size.
Potential reduce by 61.3 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. Teapea.co.nz needs all CSS files to be minified and compressed as it can save up to 61.3 kB or 86% of the original size.
Number of requests can be reduced by 8 (20%)
40
32
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tea Pea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.teapea.co.nz
599 ms
ModuleStyleSheets.css
232 ms
css
26 ms
normalize.css
456 ms
style.css
460 ms
jquery-1.8.2.min.js
690 ms
home.js
462 ms
Box.css
463 ms
Java_Box.js
469 ms
Java_DynMenusSelectedCSS.js
729 ms
analytics.js
30 ms
logo-2015.png
231 ms
search-buttonicon.png
229 ms
social-instagram.png
236 ms
social-pinterest.png
232 ms
social-facebook.png
229 ms
social-twitter.png
232 ms
sidebar-scallop.png
455 ms
Tea_Pea_School_Easter_Goodies_Slideshow.jpg
685 ms
Society_Wanderers_Sheepskin_Slideshow.jpg
459 ms
Tea_Pea_DTTW_Daybed_Slideshow.jpg
1149 ms
The_Beach_People_Slideshow1.jpg
920 ms
Sunnylife_In_Store_Slideshow.jpg
936 ms
Tea_Pea_Misery_Guts_Felted_Cushion_Insitu_Slideshow.jpg
909 ms
Sage_Clare_Slideshow1.jpg
917 ms
Feliz_New_Slideshow.jpg
1137 ms
Kirstin_Ash_Collect_Slideshow.jpg
1364 ms
Tea_Pea_DTTW_1_Slideshow.jpg
1377 ms
Tea_Pea_Kirstin_Ash_Rings_Slideshow.png
4142 ms
Tea_Pea_Izola_Slideshow.jpeg
1403 ms
Find_our_store.jpg
1364 ms
Tea_Pea_Kollab_Poly_Cafe_Small_Insitu.jpg
1377 ms
Tea_Pea_Sage_Clare_Bean_Bag_Ellery_Dot_Stitch_Insitu.jpg
1590 ms
Tea_Pea_Muskhane_Chakati_Felt_Cushions_Chairs_Insitu.jpg
1591 ms
Tea_Pea_Our_Blog.jpg
1605 ms
Tea_Pea_Odeme_Nail_Kit_Insitu.jpg
1607 ms
Tea_Pea_Cabin_Co_Throw_Arrows_Copper_Insitu.jpg
1637 ms
Tea_Pea_Uashmama_Pochette_Insitu1.jpg
1816 ms
Tea_Pea_Pencil_Hammer_Art_Print_Blue_Scooter_Insitu.jpg
1818 ms
Tea_Pea_The_Beach_People_Towel_The_Montauk_Insitu.jpg
1835 ms
collect
12 ms
teapea.co.nz accessibility score
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 input fields do not have accessible names
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
teapea.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
teapea.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teapea.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 Teapea.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.
teapea.co.nz
Open Graph description is not detected on the main page of Tea Pea. 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: