Tools & Wizards About Us
xrt.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

xrt.com

Logiciels et solutions de gestion d'entreprise Sage | Sage France

Page Load Speed

2.2 sec in total

First Response

59 ms

Resources Loaded

1.7 sec

Page Rendered

399 ms

xrt.com screenshot

About Website

Welcome to xrt.com homepage info - get ready to check Xrt best content right away, or after learning these important things about xrt.com

Accompagnez la croissance de votre entreprise avec Sage. Découvrez les logiciels et solutions de gestion Sage adaptés à vos besoins.

Visit xrt.com

Key Findings

We analyzed Xrt.com page load time and found that the first response time was 59 ms and then it took 2.1 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

xrt.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value2,160 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.998

2/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

xrt.com

59 ms

fr-fr

177 ms

887 ms

main.css

86 ms

lux.js

23 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Xrt.com, 63% (22 requests) were made to Sage.com and 26% (9 requests) were made to Fonts.sage.com. The less responsive or slowest element that took the longest time to load (887 ms) relates to the external source Sage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 390.5 kB (36%)

Content Size

1.1 MB

After Optimization

694.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xrt.com main page is 1.1 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. 70% of websites need less resources to load. Javascripts take 475.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 351.0 kB

  • Original 438.0 kB
  • After minification 437.4 kB
  • After compression 87.0 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 351.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.7 kB
  • After minification 1.7 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. Xrt images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 27.2 kB

  • Original 475.8 kB
  • After minification 475.8 kB
  • After compression 448.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 12.3 kB

  • Original 169.0 kB
  • After minification 169.0 kB
  • After compression 156.7 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. Xrt.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (73%)

Requests Now

22

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xrt.com

xrt.com

59 ms

fr-fr

fr-fr

177 ms

887 ms

main.css

main.css

86 ms

lux.js

lux.js

23 ms

utag.sync.js

utag.sync.js

54 ms

VisitorIdentification.js

VisitorIdentification.js

62 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

220 ms

jquery.validate.min.js

jquery.validate.min.js

68 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

53 ms

jquery.unobtrusive-ajax.min.js

jquery.unobtrusive-ajax.min.js

57 ms

form.validate.js

form.validate.js

232 ms

form.tracking.js

form.tracking.js

233 ms

form.conditions.js

form.conditions.js

234 ms

rantandrave.js

rantandrave.js

234 ms

formsextensions.validate.js

formsextensions.validate.js

235 ms

dotlottie-player.js

dotlottie-player.js

30 ms

require.settings.js

require.settings.js

233 ms

SageDotCom.bundle.config.js

SageDotCom.bundle.config.js

234 ms

require.js

require.js

234 ms

sage-logo-green.svg

sage-logo-green.svg

173 ms

home-redesign-hero-bg-pattern-wave-png-2.png

home-redesign-hero-bg-pattern-wave-png-2.png

175 ms

pencil.svg

pencil.svg

173 ms

Sage_Text-Regular.woff

Sage_Text-Regular.woff

236 ms

Sage_Text-Medium.woff

Sage_Text-Medium.woff

261 ms

Sage_Text-Light.woff

Sage_Text-Light.woff

262 ms

Sage_Text-Bold.woff

Sage_Text-Bold.woff

261 ms

Sage-UI-Icons.woff

Sage-UI-Icons.woff

107 ms

Sage_Headline-Black.woff

Sage_Headline-Black.woff

109 ms

Sage_UI-Regular.woff

Sage_UI-Regular.woff

108 ms

Sage_UI-Medium.woff

Sage_UI-Medium.woff

108 ms

Sage_UI-Bold.woff

Sage_UI-Bold.woff

107 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

156 ms

image-sprites-social-icons.svg

image-sprites-social-icons.svg

75 ms

SageDotCom.bundle.js

SageDotCom.bundle.js

117 ms

Accessibility Review

xrt.com accessibility score

97

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

xrt.com 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

Missing source maps for large first-party JavaScript

SEO Factors

xrt.com SEO score

92

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xrt.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Xrt.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

xrt.com

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