Tools & Wizards About Us
xabber.org screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

xabber.org

Xabber - open-source XMPP client for Android and Web

Page Load Speed

2.1 sec in total

First Response

220 ms

Resources Loaded

1.5 sec

Page Rendered

323 ms

xabber.org screenshot

About Website

Welcome to xabber.org homepage info - get ready to check Xabber best content for Russia right away, or after learning these important things about xabber.org

Register XMPP account for free. All the Xabber features, Professionally maintained, Avaliable on multiple platforms, Device Synchronization and more.

Visit xabber.org

Key Findings

We analyzed Xabber.org page load time and found that the first response time was 220 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

xabber.org performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

xabber.org

220 ms

www.xabber.com

618 ms

css

43 ms

xabber.css

82 ms

font-awesome.css

162 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Xabber.org, 74% (23 requests) were made to Xabber.com and 13% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (618 ms) relates to the external source Xabber.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.9 kB (12%)

Content Size

297.3 kB

After Optimization

262.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xabber.org main page is 297.3 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. 20% of websites need less resources to load. Images take 215.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 15.6 kB

  • Original 19.7 kB
  • After minification 13.0 kB
  • After compression 4.2 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 6.8 kB, which is 34% 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 15.6 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 16.9 kB

  • Original 215.0 kB
  • After minification 198.1 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. Xabber images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 663 B

  • Original 52.6 kB
  • After minification 52.6 kB
  • After compression 52.0 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

-18%

Potential reduce by 1.7 kB

  • Original 9.9 kB
  • After minification 9.9 kB
  • After compression 8.1 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. Xabber.org needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (20%)

Requests Now

25

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xabber.org

xabber.org

220 ms

www.xabber.com

www.xabber.com

618 ms

css

css

43 ms

xabber.css

xabber.css

82 ms

font-awesome.css

font-awesome.css

162 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

324 ms

set_ajax_csrftoken.min.js

set_ajax_csrftoken.min.js

243 ms

feedback.js

feedback.js

243 ms

xabber.js

xabber.js

245 ms

gtm.js

gtm.js

59 ms

matomo.js

matomo.js

496 ms

logo.png

logo.png

78 ms

overlay.png

overlay.png

207 ms

temp-display.jpg

temp-display.jpg

386 ms

Xabber-for-Android-display.png

Xabber-for-Android-display.png

237 ms

Xabber-for-Web-display.png

Xabber-for-Web-display.png

236 ms

latest_features_wPBAq2J-display.png

latest_features_wPBAq2J-display.png

236 ms

chevron_right.svg

chevron_right.svg

237 ms

professionally_maintained_AbH4TQl-display.png

professionally_maintained_AbH4TQl-display.png

287 ms

multiple_platforms_F1sQuMy-display.png

multiple_platforms_F1sQuMy-display.png

310 ms

device_synchronization_k1NL2bM-display.png

device_synchronization_k1NL2bM-display.png

310 ms

Button-scroll-up.svg

Button-scroll-up.svg

313 ms

Facebook_White.png

Facebook_White.png

311 ms

Twitter_White.png

Twitter_White.png

368 ms

Google__White.png

Google__White.png

387 ms

Github_White.png

Github_White.png

387 ms

redsolution.svg

redsolution.svg

387 ms

KFOmCnqEu92Fr1Mu5mxP.ttf

KFOmCnqEu92Fr1Mu5mxP.ttf

58 ms

KFOlCnqEu92Fr1MmEU9fABc9.ttf

KFOlCnqEu92Fr1MmEU9fABc9.ttf

71 ms

KFOlCnqEu92Fr1MmSU5fABc9.ttf

KFOlCnqEu92Fr1MmSU5fABc9.ttf

101 ms

KFOlCnqEu92Fr1MmWUlfABc9.ttf

KFOlCnqEu92Fr1MmWUlfABc9.ttf

107 ms

Accessibility Review

xabber.org accessibility score

91

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.

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

Links do not have a discernible name

Best Practices

xabber.org 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

SEO Factors

xabber.org SEO score

85

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

xabber.org

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