Access zamatea.com. Home | Zama Tea and Kombucha

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.7 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value4,470 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.031

2/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

www.zamatea.com

1813 ms

normalize.css

120 ms

style.css

200 ms

prettyPhoto.css

128 ms

grid.css

131 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 87% of them (65 requests) were addressed to the original Zamatea.com, 5% (4 requests) were made to Yourgreenteastore.com and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Zamatea.com.

Content Size

2.4 MB

After Optimization

1.6 MB

In fact, the total size of Zamatea.com main page is 2.4 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.5 kB

Original 45.2 kB
After minification 39.7 kB
After compression 9.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. This page needs HTML code to be minified as it can gain 5.4 kB, which is 12% 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 35.5 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 25.2 kB

Original 1.4 MB
After minification 1.3 MB

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. Zama Tea images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 550.9 kB

Original 781.1 kB
After minification 693.1 kB
After compression 230.2 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 550.9 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 196.3 kB

Original 235.4 kB
After minification 204.1 kB
After compression 39.2 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. Zamatea.com needs all CSS files to be minified and compressed as it can save up to 196.3 kB or 83% of the original size.

Requests Now

After Optimization

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zama 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 35 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zamatea.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Zamatea.com 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.

Social Sharing Optimization

zamatea.com

Open Graph data is detected on the main page of Zama Tea. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Home | Zama Tea and Kombucha

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.zamatea.com

normalize.css

style.css

prettyPhoto.css

grid.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.zamatea.com

normalize.css

style.css

prettyPhoto.css

grid.css

owl.carousel.css

responsive.css

font-awesome.min.css

prettyPhoto.css

wp-video-lightbox.css

styles.css

woocommerce-layout.css

woocommerce.css

pagenavi-css.css

wacp-frontend.css

form-basic.min.css

wpgmza_style.css

jquery-1.12.0.min.js

jquery.easing.1.3.js

superfish.js

jquery.prettyPhoto.js

jquery.nivo.slider.js

easyTooltip.js

jquery.loader.js

cufon-yui.js

James_Fajardo_400.font.js

swfobject.js

jquery.cycle.all.js

jquery.insetBorderEffect.js

owl.carousel.js

custom.js

jquery.prettyPhoto.js

video-lightbox.js

myriad-pro.cufonfonts.js

cufon-replace.js

jquery.twitter.js

jquery.flickrush.js

audio.js

comment-reply.min.js

jquery.form.min.js

scripts.js

add-to-cart.min.js

jquery.blockUI.min.js