Tools & Wizards About Us
xcelpay.io screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

xcelpay.io

Page Load Speed

251 ms in total

First Response

35 ms

Resources Loaded

158 ms

Page Rendered

58 ms

xcelpay.io screenshot

About Website

Click here to check amazing Xcelpay content. Otherwise, check out these important facts you probably never knew about xcelpay.io

XcelPay, the self-custodial multi-chain crypto wallet, integrates Wallet, Buy & Swap, Launchpad, Marketplace, XcelTrip - Travel with Crypto in a single app.

Visit xcelpay.io

Key Findings

We analyzed Xcelpay.io page load time and found that the first response time was 35 ms and then it took 216 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

xcelpay.io performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

95/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value3,750 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

xcelpay.io

35 ms

xcelpay.io

31 ms

e891ff8067aa2b39.css

10 ms

ea8345fbbb84e9a9.css

17 ms

polyfills-c67a75d1b6f99dc8.js

32 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that all of those requests were addressed to Xcelpay.io and no external sources were called. The less responsive or slowest element that took the longest time to load (89 ms) belongs to the original domain Xcelpay.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 320.4 kB (45%)

Content Size

715.4 kB

After Optimization

394.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xcelpay.io main page is 715.4 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. 45% of websites need less resources to load. Images take 394.0 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 139.9 kB

  • Original 162.2 kB
  • After minification 162.2 kB
  • After compression 22.3 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 139.9 kB or 86% of the original size.

Image Optimization

-12%

Potential reduce by 48.9 kB

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

JavaScript Optimization

-68%

Potential reduce by 6.6 kB

  • Original 9.8 kB
  • After minification 9.8 kB
  • After compression 3.2 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 6.6 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 125.0 kB

  • Original 149.2 kB
  • After minification 149.2 kB
  • After compression 24.2 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. Xcelpay.io needs all CSS files to be minified and compressed as it can save up to 125.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (81%)

Requests Now

21

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xcelpay.io

xcelpay.io

35 ms

xcelpay.io

xcelpay.io

31 ms

e891ff8067aa2b39.css

e891ff8067aa2b39.css

10 ms

ea8345fbbb84e9a9.css

ea8345fbbb84e9a9.css

17 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

32 ms

webpack-a1e031a2581f8176.js

webpack-a1e031a2581f8176.js

20 ms

framework-89f2f7d214569455.js

framework-89f2f7d214569455.js

32 ms

main-a3f92f7ad5299c71.js

main-a3f92f7ad5299c71.js

53 ms

_app-433244faa99ee999.js

_app-433244faa99ee999.js

73 ms

94726e6d-76df4679973d0d14.js

94726e6d-76df4679973d0d14.js

73 ms

ed81d8d0-97e2c48907f38604.js

ed81d8d0-97e2c48907f38604.js

78 ms

1954-67f3b71668a89ce5.js

1954-67f3b71668a89ce5.js

76 ms

5675-962616bed1fd52a0.js

5675-962616bed1fd52a0.js

76 ms

3537-280241f819903241.js

3537-280241f819903241.js

76 ms

990-67225411b69dce23.js

990-67225411b69dce23.js

76 ms

3425-c9721bb5b2e0c544.js

3425-c9721bb5b2e0c544.js

76 ms

9281-c973c487cb4b70cc.js

9281-c973c487cb4b70cc.js

87 ms

760-0b88139e70136c87.js

760-0b88139e70136c87.js

87 ms

2289-39142897a7d23e73.js

2289-39142897a7d23e73.js

87 ms

index-acfa5678df05fd4a.js

index-acfa5678df05fd4a.js

88 ms

_buildManifest.js

_buildManifest.js

88 ms

_ssgManifest.js

_ssgManifest.js

89 ms

bg.f6d23831.webp

bg.f6d23831.webp

75 ms

Accessibility Review

xcelpay.io 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

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

xcelpay.io 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

xcelpay.io SEO score

92

Search Engine Optimization Advices

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 Xcelpay.io 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 Xcelpay.io 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

xcelpay.io

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