Tools & Wizards About Us
fadata.bg screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fadata.bg

Fadata | Innovative Insurance Software and IT Solutions

Page Load Speed

3.4 sec in total

First Response

499 ms

Resources Loaded

2.6 sec

Page Rendered

222 ms

fadata.bg screenshot

About Website

Click here to check amazing Fadata content for Bulgaria. Otherwise, check out these important facts you probably never knew about fadata.bg

Provides Innovative Insurance and IT Solutions for General, Life, Health and Takaful with more than 60 customers on five continents and a team of qualified professionals

Visit fadata.bg

Key Findings

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

Performance Metrics

fadata.bg performance score

0

Network Requests Diagram

fadata.bg

499 ms

www.fadata.eu

606 ms

language-selector.css

144 ms

style.css

387 ms

wp-modal-login.css

268 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fadata.bg, 65% (22 requests) were made to Fadata.eu and 18% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (842 ms) relates to the external source Fadata.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 240.4 kB (26%)

Content Size

941.7 kB

After Optimization

701.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fadata.bg main page is 941.7 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. 30% of websites need less resources to load. Images take 642.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 21.4 kB

  • Original 27.3 kB
  • After minification 24.4 kB
  • After compression 5.9 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 3.0 kB, which is 11% 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 21.4 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 9.2 kB

  • Original 642.9 kB
  • After minification 633.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. Fadata images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 111.9 kB

  • Original 157.6 kB
  • After minification 128.8 kB
  • After compression 45.7 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 111.9 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 97.8 kB

  • Original 113.8 kB
  • After minification 89.6 kB
  • After compression 16.0 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. Fadata.bg needs all CSS files to be minified and compressed as it can save up to 97.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (67%)

Requests Now

27

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fadata.bg

fadata.bg

499 ms

www.fadata.eu

www.fadata.eu

606 ms

language-selector.css

language-selector.css

144 ms

style.css

style.css

387 ms

wp-modal-login.css

wp-modal-login.css

268 ms

jquery.min.js

jquery.min.js

26 ms

brp1ezx.js

brp1ezx.js

134 ms

wp-modal-login.min.js

wp-modal-login.min.js

282 ms

swipe.js

swipe.js

280 ms

jquery.scrollTo.js

jquery.scrollTo.js

278 ms

jquery.nav.js

jquery.nav.js

288 ms

v.plugin.gmaps.js

v.plugin.gmaps.js

413 ms

obfuscateEmail.js

obfuscateEmail.js

416 ms

jquery.isotope.min.js

jquery.isotope.min.js

420 ms

jquery.pietimer.js

jquery.pietimer.js

421 ms

jquery.stellar.min.js

jquery.stellar.min.js

432 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

505 ms

fadata.js

fadata.js

525 ms

sitepress.js

sitepress.js

597 ms

www.fadata.eu

www.fadata.eu

128 ms

analytics.js

analytics.js

60 ms

sprites.png

sprites.png

286 ms

fadata-logo.png

fadata-logo.png

151 ms

insis-freedom.jpg

insis-freedom.jpg

710 ms

map.jpg

map.jpg

842 ms

office-light.jpg

office-light.jpg

507 ms

collect

collect

14 ms

UIYMwGx0LuWrDD3emvxaFPrUhyg43RStBk7HR2IeLLCffHPsgsMWeMJ6Mk6f5Mb.woff

UIYMwGx0LuWrDD3emvxaFPrUhyg43RStBk7HR2IeLLCffHPsgsMWeMJ6Mk6f5Mb.woff

37 ms

Hmr_zxzdHaIHyPxzdF1ZAPnKmKqFWnXaX8ktGiP9mwSffHHsgsMWeMJ6Mk6f5Mw.woff

Hmr_zxzdHaIHyPxzdF1ZAPnKmKqFWnXaX8ktGiP9mwSffHHsgsMWeMJ6Mk6f5Mw.woff

68 ms

gPj0djVu1JBjQJslz39e6n4fQZxyz6--jy1-K-qqan6ff4kQgsMWeMJ6Mk6f5MS.woff

gPj0djVu1JBjQJslz39e6n4fQZxyz6--jy1-K-qqan6ff4kQgsMWeMJ6Mk6f5MS.woff

106 ms

xdTJgGPceUw_jFpWRob1HPV55RdyT8Hr5R78KovHzbCffHAsgsMWeMJ6Mk6f5Mt.woff

xdTJgGPceUw_jFpWRob1HPV55RdyT8Hr5R78KovHzbCffHAsgsMWeMJ6Mk6f5Mt.woff

136 ms

collect

collect

65 ms

p.gif

p.gif

130 ms

print.css

print.css

144 ms

SEO Factors

fadata.bg SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

fadata.bg

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