Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fts.bg

Dynamics 365, ERP, CRM, Deltek Maconomy, ClickDimensions

Page Load Speed

8.9 sec in total

First Response

1.2 sec

Resources Loaded

7.5 sec

Page Rendered

253 ms

fts.bg screenshot

About Website

Visit fts.bg now to see the best up-to-date Fts content and also check out these interesting facts you probably never knew about fts.bg

ERP and CRM systems, based on innovative technologies with integrated best practices and adapted to the local business models.

Visit fts.bg

Key Findings

We analyzed Fts.bg page load time and found that the first response time was 1.2 sec and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

fts.bg performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

fts.bg

1169 ms

style.css

909 ms

css

30 ms

jquery-1.11.1.min.js

1111 ms

jquery-migrate-1.0.0.js

643 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 89% of them (129 requests) were addressed to the original Fts.bg, 6% (9 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Fts.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 912.7 kB (47%)

Content Size

2.0 MB

After Optimization

1.0 MB

In fact, the total size of Fts.bg main page is 2.0 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 38.8 kB

  • Original 46.6 kB
  • After minification 38.8 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 7.9 kB, which is 17% 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 38.8 kB or 83% of the original size.

Image Optimization

-31%

Potential reduce by 391.4 kB

  • Original 1.2 MB
  • After minification 856.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, Fts needs image optimization as it can save up to 391.4 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 235.7 kB

  • Original 372.8 kB
  • After minification 362.1 kB
  • After compression 137.1 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 235.7 kB or 63% of the original size.

CSS Optimization

-84%

Potential reduce by 246.7 kB

  • Original 295.0 kB
  • After minification 288.1 kB
  • After compression 48.3 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. Fts.bg needs all CSS files to be minified and compressed as it can save up to 246.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (8%)

Requests Now

135

After Optimization

124

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

Accessibility Review

fts.bg accessibility score

81

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-*] attributes do not match their roles

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fts.bg 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

fts.bg SEO score

86

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fts.bg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fts.bg 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 Fts. 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: