Tools & Wizards About Us
jamestea.com screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

jamestea.com

Welcome to JAMES TEA

Page Load Speed

837 ms in total

First Response

31 ms

Resources Loaded

678 ms

Page Rendered

128 ms

jamestea.com screenshot

About Website

Click here to check amazing JAMES TEA content. Otherwise, check out these important facts you probably never knew about jamestea.com

Welcome to James Tea

Visit jamestea.com

Key Findings

We analyzed Jamestea.com page load time and found that the first response time was 31 ms and then it took 806 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

jamestea.com performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

74/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

jamestea.com

31 ms

jamestea.com

18 ms

Style.aspx

221 ms

js-image-slider.css

227 ms

js-image-slider.js

227 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that all of those requests were addressed to Jamestea.com and no external sources were called. The less responsive or slowest element that took the longest time to load (338 ms) belongs to the original domain Jamestea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.8 kB (6%)

Content Size

402.6 kB

After Optimization

378.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jamestea.com main page is 402.6 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. 30% of websites need less resources to load. Images take 374.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 16.3 kB

  • Original 19.7 kB
  • After minification 15.5 kB
  • After compression 3.4 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 4.2 kB, which is 21% 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 16.3 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 6.9 kB

  • Original 374.5 kB
  • After minification 367.6 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. JAMES TEA images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 14 B

  • Original 7.1 kB
  • After minification 7.1 kB
  • After compression 7.1 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.

CSS Optimization

-47%

Potential reduce by 560 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 629 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. Jamestea.com needs all CSS files to be minified and compressed as it can save up to 560 B or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (11%)

Requests Now

65

After Optimization

58

  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JAMES TEA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

jamestea.com

jamestea.com

31 ms

jamestea.com

jamestea.com

18 ms

Style.aspx

Style.aspx

221 ms

js-image-slider.css

js-image-slider.css

227 ms

js-image-slider.js

js-image-slider.js

227 ms

generic.css

generic.css

225 ms

grey_strip.gif

grey_strip.gif

12 ms

right.gif

right.gif

10 ms

logo_top.jpg

logo_top.jpg

11 ms

web_top.jpg

web_top.jpg

13 ms

right_top.jpg

right_top.jpg

14 ms

stripe.gif

stripe.gif

13 ms

button-home%20r.gif

button-home%20r.gif

13 ms

button-order_tea-stat.gif

button-order_tea-stat.gif

68 ms

button-order_lemonade-stat.gif

button-order_lemonade-stat.gif

230 ms

button-testimonals.gif

button-testimonals.gif

25 ms

button-instruct.gif

button-instruct.gif

25 ms

button-facts.gif

button-facts.gif

24 ms

buttons_contact.gif

buttons_contact.gif

68 ms

button-newsletter.gif

button-newsletter.gif

26 ms

button_distribute.gif

button_distribute.gif

26 ms

image-slider-5.jpg

image-slider-5.jpg

338 ms

image-slider-4.jpg

image-slider-4.jpg

176 ms

image-slider-3.jpg

image-slider-3.jpg

174 ms

leftcrnrtop.gif

leftcrnrtop.gif

67 ms

line_top.gif

line_top.gif

68 ms

rightcrnrtop.gif

rightcrnrtop.gif

69 ms

leftside.gif

leftside.gif

70 ms

front-bottom.gif

front-bottom.gif

71 ms

fresh_brewed.png

fresh_brewed.png

71 ms

(button)%20order%20now.png

(button)%20order%20now.png

126 ms

divider.gif

divider.gif

124 ms

conveince.png

conveince.png

180 ms

(button)%20learn_more.png

(button)%20learn_more.png

181 ms

caffree.png

caffree.png

175 ms

rightside.gif

rightside.gif

176 ms

leftcrnrbttm.gif

leftcrnrbttm.gif

176 ms

rightrbttmcrnr.gif

rightrbttmcrnr.gif

177 ms

left.gif

left.gif

177 ms

bottom_left.gif

bottom_left.gif

176 ms

bottom_purple.gif

bottom_purple.gif

173 ms

bottom_right.gif

bottom_right.gif

173 ms

logos.jpg

logos.jpg

173 ms

facebookIcon.gif

facebookIcon.gif

226 ms

(logo)kosher.jpg

(logo)kosher.jpg

226 ms

loading.gif

loading.gif

278 ms

creme_bgkrnd.gif

creme_bgkrnd.gif

171 ms

line_bottom.gif

line_bottom.gif

171 ms

bullet.png

bullet.png

212 ms

print.aspx

print.aspx

56 ms

(button)%20order%20now%20r.png

(button)%20order%20now%20r.png

4 ms

(button)%20learn_more%20r.png

(button)%20learn_more%20r.png

4 ms

button-products%20r.gif

button-products%20r.gif

4 ms

button-placeorder%20r.gif

button-placeorder%20r.gif

4 ms

button-testimonals%20r.gif

button-testimonals%20r.gif

5 ms

button-instruct%20r.gif

button-instruct%20r.gif

5 ms

button-facts%20r.gif

button-facts%20r.gif

6 ms

buttons_contact%20r.gif

buttons_contact%20r.gif

6 ms

button-newsletter%20r.gif

button-newsletter%20r.gif

6 ms

button_distribute%20r.gif

button_distribute%20r.gif

7 ms

button-home.gif

button-home.gif

6 ms

button-products%20d.gif

button-products%20d.gif

7 ms

button-placeorder%20d.gif

button-placeorder%20d.gif

8 ms

button-testimonals%20d.gif

button-testimonals%20d.gif

8 ms

button-instruct%20d.gif

button-instruct%20d.gif

9 ms

button-facts%20d.gif

button-facts%20d.gif

8 ms

buttons_contact%20d.gif

buttons_contact%20d.gif

9 ms

button-newsletter%20d.gif

button-newsletter%20d.gif

8 ms

button_distribute%20d.gif

button_distribute%20d.gif

9 ms

button-home%20d.gif

button-home%20d.gif

9 ms

Accessibility Review

jamestea.com accessibility score

54

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

jamestea.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

jamestea.com SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jamestea.com 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 Jamestea.com 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.

Social Sharing Optimization

jamestea.com

Open Graph description is not detected on the main page of JAMES 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: