Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

Page Load Speed

11.3 sec in total

First Response

1.5 sec

Resources Loaded

8.6 sec

Page Rendered

1.2 sec

mateo.in screenshot

About Website

Click here to check amazing Mateo content for India. Otherwise, check out these important facts you probably never knew about mateo.in

Mateo - Chamomile Green Tea, Silver Needles Tea, Halmari Golden Tippy Orthodox, Golden Needles Tea, Chamomile Green Tea, The Sampler pack and Free Shipping above INR 500.

Visit mateo.in

Key Findings

We analyzed Mateo.in page load time and found that the first response time was 1.5 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

mateo.in performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value20.3 s

0/100

10%

TBT (Total Blocking Time)

Value17,250 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

www.mateo.in

1500 ms

js

143 ms

wp-emoji-release.min.js

119 ms

style.min.css

199 ms

jquery.selectBox.css

249 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 84% of them (103 requests) were addressed to the original Mateo.in, 9% (11 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Mateo.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (65%)

Content Size

3.6 MB

After Optimization

1.2 MB

In fact, the total size of Mateo.in main page is 3.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 127.2 kB

  • Original 144.0 kB
  • After minification 133.9 kB
  • After compression 16.8 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 127.2 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 234 B

  • Original 766.5 kB
  • After minification 766.3 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. Mateo images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 585.5 kB

  • Original 834.4 kB
  • After minification 786.2 kB
  • After compression 248.9 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 585.5 kB or 70% of the original size.

CSS Optimization

-88%

Potential reduce by 1.6 MB

  • Original 1.8 MB
  • After minification 1.6 MB
  • After compression 212.5 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. Mateo.in needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (62%)

Requests Now

105

After Optimization

40

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

Accessibility Review

mateo.in accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

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.

Best Practices

mateo.in best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

mateo.in SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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 Mateo.in 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 Mateo.in 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

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