Tools & Wizards About Us
fexopay.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

fexopay.com

FexoPay - Международни парични преводи и платежни услуги

Page Load Speed

4.2 sec in total

First Response

377 ms

Resources Loaded

3.5 sec

Page Rendered

359 ms

fexopay.com screenshot

About Website

Visit fexopay.com now to see the best up-to-date Fexo Pay content for Bulgaria and also check out these interesting facts you probably never knew about fexopay.com

Fexopay Money Transfer - международни парични преводи, плащане на битови сметки и данъци в България, превод по банкова сметка, бизнес за българи в чужбина.

Visit fexopay.com

Key Findings

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

Performance Metrics

fexopay.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

fexopay.com

377 ms

fexopay.com

769 ms

fexopay-style-sheet.css

355 ms

aosan.css

443 ms

animate.css

591 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 83% of them (30 requests) were addressed to the original Fexopay.com, 14% (5 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Fexopay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.7 kB (75%)

Content Size

35.5 kB

After Optimization

8.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fexopay.com main page is 35.5 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. HTML takes 31.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 26.2 kB

  • Original 31.2 kB
  • After minification 22.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 8.4 kB, which is 27% 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 26.2 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.2 kB
  • After minification 2.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. Fexo Pay images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 220 B

  • Original 996 B
  • After minification 996 B
  • After compression 776 B

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

CSS Optimization

-25%

Potential reduce by 252 B

  • Original 996 B
  • After minification 968 B
  • After compression 744 B

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. Fexopay.com needs all CSS files to be minified and compressed as it can save up to 252 B or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (24%)

Requests Now

29

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fexopay.com

fexopay.com

377 ms

fexopay.com

fexopay.com

769 ms

fexopay-style-sheet.css

fexopay-style-sheet.css

355 ms

aosan.css

aosan.css

443 ms

animate.css

animate.css

591 ms

bootstrap.min.css

bootstrap.min.css

825 ms

css2

css2

31 ms

unpkg.js

unpkg.js

479 ms

aos.js

aos.js

481 ms

jquery.min.js

jquery.min.js

967 ms

bootstrap.min.js

bootstrap.min.js

1071 ms

logo_fexoPay-06.svg

logo_fexoPay-06.svg

513 ms

easypay.svg

easypay.svg

117 ms

slider_5.jpg

slider_5.jpg

747 ms

slide1.jpg

slide1.jpg

755 ms

slide31.jpg

slide31.jpg

751 ms

slide2-xl1.jpg

slide2-xl1.jpg

629 ms

services.png

services.png

516 ms

bisness_background.jpg

bisness_background.jpg

749 ms

bisness.png

bisness.png

627 ms

logo_ria.svg

logo_ria.svg

742 ms

logo_upt-01.svg

logo_upt-01.svg

757 ms

logo_mg.svg

logo_mg.svg

855 ms

logo_moneytrans.svg

logo_moneytrans.svg

867 ms

logo_cashline.svg

logo_cashline.svg

868 ms

map.png

map.png

872 ms

contacts.png

contacts.png

1116 ms

place.svg

place.svg

876 ms

phonec.svg

phonec.svg

967 ms

email.svg

email.svg

1393 ms

fexopay_white.svg

fexopay_white.svg

1394 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

16 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

26 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

32 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

42 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

42 ms

Accessibility Review

fexopay.com accessibility score

95

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

fexopay.com best practices score

75

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fexopay.com SEO score

81

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

    BG

  • Language Claimed

    BG

  • Encoding

    UTF-8

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

fexopay.com

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