Tools & Wizards About Us
ofi.bg screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

ofi.bg

Всички оферти за колективно пазаруване на едно място | Ofi.bg

Page Load Speed

2.5 sec in total

First Response

364 ms

Resources Loaded

2 sec

Page Rendered

119 ms

ofi.bg screenshot

About Website

Click here to check amazing Ofi content. Otherwise, check out these important facts you probably never knew about ofi.bg

Всички оферти за колективно пазаруване на едно място! Ofi.bg намира всички най-изгодни оферти вместо Вас!

Visit ofi.bg

Key Findings

We analyzed Ofi.bg page load time and found that the first response time was 364 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ofi.bg performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value5.7 s

50/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

ofi.bg

364 ms

739 ms

jq-ui.css

344 ms

jqtransform.css

238 ms

layout_complete.css

444 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 69% of them (24 requests) were addressed to the original Ofi.bg, 6% (2 requests) were made to Googleadservices.com and 6% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (739 ms) belongs to the original domain Ofi.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.4 kB (23%)

Content Size

402.9 kB

After Optimization

310.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ofi.bg main page is 402.9 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. 35% of websites need less resources to load. Javascripts take 266.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 33.2 kB

  • Original 42.4 kB
  • After minification 37.9 kB
  • After compression 9.2 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 4.6 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 33.2 kB or 78% of the original size.

Image Optimization

-13%

Potential reduce by 9.3 kB

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

JavaScript Optimization

-17%

Potential reduce by 46.0 kB

  • Original 266.2 kB
  • After minification 266.2 kB
  • After compression 220.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 46.0 kB or 17% of the original size.

CSS Optimization

-16%

Potential reduce by 3.8 kB

  • Original 23.1 kB
  • After minification 23.1 kB
  • After compression 19.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. Ofi.bg needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (45%)

Requests Now

31

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ofi. 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 as a result speed up the page load time.

Network Requests Diagram

ofi.bg

ofi.bg

364 ms

739 ms

jq-ui.css

jq-ui.css

344 ms

jqtransform.css

jqtransform.css

238 ms

layout_complete.css

layout_complete.css

444 ms

jquery.debug.js

jquery.debug.js

673 ms

jq-ui.js

jq-ui.js

568 ms

jqtransform.js

jqtransform.js

339 ms

jq_touch.min.js

jq_touch.min.js

365 ms

hashchange.js

hashchange.js

465 ms

conversion.js

conversion.js

88 ms

jsapi

jsapi

8 ms

clusters.js

clusters.js

365 ms

main_complete.js

main_complete.js

488 ms

maps.generate.js

maps.generate.js

449 ms

loader.js

loader.js

17 ms

pattern.gif

pattern.gif

145 ms

left_pattern.jpg

left_pattern.jpg

129 ms

logo-ofi-transparent.gif

logo-ofi-transparent.gif

128 ms

ofi_slogan.gif

ofi_slogan.gif

127 ms

sprite.png

sprite.png

344 ms

fb_dynamic_animation.png

fb_dynamic_animation.png

126 ms

loader.gif

loader.gif

127 ms

overlay_bg.png

overlay_bg.png

230 ms

ga.js

ga.js

12 ms

97 ms

__utm.gif

__utm.gif

15 ms

js

js

110 ms

all.js

all.js

19 ms

checkbox.gif

checkbox.gif

128 ms

select_left.gif

select_left.gif

128 ms

select_right.gif

select_right.gif

129 ms

54 ms

all.js

all.js

6 ms

27 ms

Accessibility Review

ofi.bg accessibility score

77

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.

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

ofi.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

SEO Factors

ofi.bg SEO score

82

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

ofi.bg

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