Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

gepi.bg

Gepi.bg оферти за групово пазаруване с ваучери, отстъпки и промоции от цялата страна. - gepi.bg

Page Load Speed

6.5 sec in total

First Response

1.4 sec

Resources Loaded

4.4 sec

Page Rendered

614 ms

gepi.bg screenshot

About Website

Welcome to gepi.bg homepage info - get ready to check Gepi best content for Bulgaria right away, or after learning these important things about gepi.bg

Оферти за групово пазаруване – ваучери, отстъпки и промоции в София

Visit gepi.bg

Key Findings

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

Performance Metrics

gepi.bg performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

gepi.bg

1406 ms

styles.css

456 ms

jquery.fancybox-1.3.4.css

311 ms

jquery-ui-1.8.18.custom.css

477 ms

jquery.countdown.css

323 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 56% of them (62 requests) were addressed to the original Gepi.bg, 14% (15 requests) were made to Scontent.xx.fbcdn.net and 11% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Gepi.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 427.0 kB (34%)

Content Size

1.2 MB

After Optimization

821.2 kB

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

HTML Optimization

-85%

Potential reduce by 81.3 kB

  • Original 95.8 kB
  • After minification 81.8 kB
  • After compression 14.5 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 14.0 kB, which is 15% 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 81.3 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 36.6 kB

  • Original 716.7 kB
  • After minification 680.1 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. Gepi images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 250.8 kB

  • Original 365.4 kB
  • After minification 365.1 kB
  • After compression 114.6 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 250.8 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 58.3 kB

  • Original 70.4 kB
  • After minification 68.1 kB
  • After compression 12.1 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. Gepi.bg needs all CSS files to be minified and compressed as it can save up to 58.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (43%)

Requests Now

107

After Optimization

61

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

Accessibility Review

gepi.bg accessibility score

83

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

gepi.bg best practices score

42

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

gepi.bg SEO score

54

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Gepi.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 Gepi.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 Gepi. 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: