Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

btru.st

Accueil - ITinSell Software

Page Load Speed

5.1 sec in total

First Response

309 ms

Resources Loaded

4.3 sec

Page Rendered

543 ms

btru.st screenshot

About Website

Click here to check amazing Btru content for Ukraine. Otherwise, check out these important facts you probably never knew about btru.st

ITinSell édite un logiciel à destination de la elogistique permettant une nouvelle expérience de livraison ecommerce pour le destinataire.

Visit btru.st

Key Findings

We analyzed Btru.st page load time and found that the first response time was 309 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

btru.st performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value16,650 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value29.3 s

0/100

10%

Network Requests Diagram

btru.st

309 ms

itinsell.com

488 ms

MonJS

97 ms

analytics.js

37 ms

sw2.js

639 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Btru.st, 92% (71 requests) were made to Itinsell.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Itinsell.com.

Page Optimization Overview & Recommendations

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

Content Size

406.2 kB

After Optimization

341.8 kB

In fact, the total size of Btru.st main page is 406.2 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. 40% of websites need less resources to load. Images take 314.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.2 kB

  • Original 70.9 kB
  • After minification 66.1 kB
  • After compression 14.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 56.2 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 8.1 kB

  • Original 314.3 kB
  • After minification 306.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. Btru images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 23 (31%)

Requests Now

74

After Optimization

51

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Btru. 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.

Accessibility Review

btru.st accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA tooltip elements do not have accessible names.

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

Links do not have a discernible name

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

btru.st best practices score

58

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

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

btru.st 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

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 Btru.st 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 Btru.st 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 Btru. 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: