3.1 sec in total
418 ms
2.1 sec
587 ms
Click here to check amazing Plymouth Tea content. Otherwise, check out these important facts you probably never knew about plymouthtea.co.uk
Plymouth Tea are passionate about the history and tradition of tea. We produce quality teas in the historic city of Plymouth, England.
Visit plymouthtea.co.ukWe analyzed Plymouthtea.co.uk page load time and found that the first response time was 418 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
plymouthtea.co.uk performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value9.2 s
1/100
25%
Value4.7 s
68/100
10%
Value680 ms
44/100
30%
Value0.455
20/100
15%
Value11.2 s
20/100
10%
418 ms
449 ms
135 ms
157 ms
134 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Plymouthtea.co.uk, 42% (35 requests) were made to Cdn.shopify.com and 24% (20 requests) were made to Az833648.vo.msecnd.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cdn.shopify.com.
Page size can be reduced by 1.6 MB (39%)
4.1 MB
2.5 MB
In fact, the total size of Plymouthtea.co.uk main page is 4.1 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. 70% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 37.9 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 8.2 kB, which is 17% 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 37.9 kB or 80% of the original size.
Potential reduce by 662.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. Obviously, Plymouth Tea needs image optimization as it can save up to 662.2 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 331.7 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 331.7 kB or 66% of the original size.
Potential reduce by 593.4 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. Plymouthtea.co.uk needs all CSS files to be minified and compressed as it can save up to 593.4 kB or 91% of the original size.
Number of requests can be reduced by 39 (53%)
74
35
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plymouth Tea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.plymouthtea.co.uk
418 ms
widget.js
449 ms
styles.css
135 ms
css
157 ms
html5shiv.js
134 ms
ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js
154 ms
jquery.min.js
165 ms
option_selection-04f21dade47c181126ac61b64d757485f84671daadfa90e4956a522cda4c2948.js
141 ms
api.jquery-5f52c6aafe08e99b5fd74bc04431f324d961490d08bb70ca69b5e05941aa4323.js
153 ms
jquery.tweet.js
150 ms
jquery.fancybox.js
159 ms
scripts.js
151 ms
beecart.js
112 ms
beacon_call.js
161 ms
shopify_stats.js
64 ms
analytics.js
115 ms
bg-custom.png
213 ms
gtm.js
146 ms
promotions.js
239 ms
icon-search.png
62 ms
icon-cart-small.png
63 ms
logo.png
64 ms
arrow-dark.png
62 ms
slideshow_1.jpg
397 ms
slideshow_2.jpg
99 ms
slideshow_3.jpg
97 ms
slideshow_4.jpg
93 ms
slideshow_5.jpg
1231 ms
slideshow_6.jpg
211 ms
slideshow_7.jpg
129 ms
Drakes_Blend_large.jpg
115 ms
Armada_Blend_large.jpg
140 ms
Mayflower_large.jpg
140 ms
Green-tea-new-front_large.jpg
164 ms
Earl_Grey_Front_large.jpg
162 ms
Decaffeinated_Front_large.jpg
194 ms
Drakes_Blend_Loose_Leaf_large.jpg
187 ms
Armada_Blend_Loose_Leaf_large.jpg
193 ms
Mayflower_Blend_Loose_Leaf_large.jpg
402 ms
social-icons-light-bg.png
212 ms
icon-cc-visa.gif
214 ms
icon-cc-mastercard.gif
219 ms
icon-cc-paypal.gif
228 ms
MViwy4K6e56oHcyeMzjbCQ.ttf
91 ms
F-uvpIj1hF17IDyvQvI50Q.ttf
94 ms
shopify.js
109 ms
beacon
41 ms
collect
28 ms
record.gif
138 ms
collect
82 ms
sdk.js
202 ms
cGx5bW91dGgtdGVhLm15c2hvcGlmeS5jb20=.js
120 ms
setting.js
75 ms
widget.css
94 ms
i
31 ms
css
45 ms
beeketing.js
53 ms
bk_app_integration.css
27 ms
front.css
53 ms
front.css
82 ms
front.css
111 ms
base.css
132 ms
front.css
140 ms
base.js
183 ms
base.js
164 ms
base.js
181 ms
base.js
129 ms
base.js
181 ms
count_visitor.json
283 ms
sdk.js
88 ms
sprites.png
119 ms
20909
452 ms
actions.json
236 ms
cart.json
162 ms
fancybox.png
66 ms
OpenSansRegular.woff
102 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
58 ms
OpenSansLight.woff
116 ms
OpenSansSemibold.woff
121 ms
OpenSansBold.woff
120 ms
101 ms
fb-icon-2.png
69 ms
xd_arbiter.php
61 ms
plymouthtea.co.uk 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
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.
plymouthtea.co.uk 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
Page has valid source maps
plymouthtea.co.uk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Plymouthtea.co.uk 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 Plymouthtea.co.uk 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.
plymouthtea.co.uk
Open Graph description is not detected on the main page of Plymouth Tea. 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: