Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

Page Load Speed

4 sec in total

First Response

377 ms

Resources Loaded

3.6 sec

Page Rendered

53 ms

xbees.in screenshot

About Website

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

Visit xbees.in

Key Findings

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

Performance Metrics

xbees.in performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

xbees.in

377 ms

xbees.in

754 ms

www.xpressbees.com

750 ms

css2

36 ms

main.859794aa.js

1293 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 33% of them (2 requests) were addressed to the original Xbees.in, 50% (3 requests) were made to Xpressbees.com and 17% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Xpressbees.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.6 kB (16%)

Content Size

1.0 MB

After Optimization

875.3 kB

In fact, the total size of Xbees.in main page is 1.0 MB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 786.9 kB which makes up the majority of the site volume.

HTML Optimization

-43%

Potential reduce by 295 B

  • Original 689 B
  • After minification 689 B
  • After compression 394 B

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 295 B or 43% of the original size.

Image Optimization

-20%

Potential reduce by 158.4 kB

  • Original 786.9 kB
  • After minification 628.4 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, Xbees needs image optimization as it can save up to 158.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 4.6 kB

  • Original 192.2 kB
  • After minification 192.2 kB
  • After compression 187.5 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

-7%

Potential reduce by 4.2 kB

  • Original 63.2 kB
  • After minification 63.2 kB
  • After compression 58.9 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. Xbees.in has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xbees. According to our analytics all requests are already optimized.

Accessibility Review

xbees.in accessibility score

98

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.

Best Practices

xbees.in best practices score

75

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

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

xbees.in SEO score

93

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

Links do not have descriptive text

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 Xbees.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 Xbees.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 description is not detected on the main page of Xbees. 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: