6.5 sec in total
1.4 sec
4.4 sec
614 ms
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.bgWe 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.
gepi.bg performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value8.3 s
2/100
25%
Value6.5 s
39/100
10%
Value240 ms
85/100
30%
Value0.075
95/100
15%
Value7.5 s
47/100
10%
1406 ms
456 ms
311 ms
477 ms
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 size can be reduced by 427.0 kB (34%)
1.2 MB
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.
Potential reduce by 81.3 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.
Potential reduce by 36.6 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.
Potential reduce by 250.8 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.
Potential reduce by 58.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. 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.
Number of requests can be reduced by 46 (43%)
107
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.
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
jcountdown.css
338 ms
jquery.min.js
924 ms
jquery-ui.min.js
1284 ms
jquery.nivo.slider.pack.js
673 ms
jquery.fancybox-1.3.4.pack.js
604 ms
jquery.tipsy.js
634 ms
init.js
667 ms
jcountdown.js
755 ms
all.js
272 ms
jquery.countdown.js
793 ms
f593339dd683df36341adb960487cf7e.jpg
2074 ms
def_logo.png
166 ms
fconnect.png
166 ms
C_d825ad5b696f7dba13f882dcb719d718.jpg
170 ms
C_5e03e72ad7b272282f3c45e1bc6f3b8f.jpg
321 ms
visa_logo.png
173 ms
mastercard_logo.png
324 ms
epaybg_logo.png
321 ms
easypay_logo.png
342 ms
bpay_logo.png
343 ms
cashterminal_logo.png
473 ms
bank1logo.jpg
480 ms
80 ms
bg_select.png
473 ms
bg_account.png
483 ms
bg_sep2.png
498 ms
bg_menu.jpg
619 ms
cats_bg.jpg
646 ms
tag.png
702 ms
bg_label.png
773 ms
bg_btn.png
774 ms
bg_timer.png
798 ms
xd_arbiter.php
250 ms
xd_arbiter.php
462 ms
icon_i.png
919 ms
bg_content_shadow.png
948 ms
bg_newsletter_offer.png
963 ms
bg_offer.png
965 ms
B_6ecdd205453b80752e0facfc88a3e4ab.jpg
1218 ms
bg_btn2.png
1080 ms
bg_timer_middle.png
1124 ms
B_c8d16980a2a67616ebd74a038432c406.jpg
1274 ms
B_046b5738a2f0d1fbbdc63dc3cec5bf39.jpg
1256 ms
B_1bbbdb993255e0b9cf1f14e58ea46802.jpg
1387 ms
B_fe698a02094e095e97fd751f13ffb6bf.jpg
1446 ms
B_ed5e19c094a1742529bb4dd47761607b.jpg
1501 ms
B_46a7ad2afab8bd944534d717bda77096.jpg
1553 ms
B_011280ef878fab2bebd8801c52ac87dd.jpg
1589 ms
B_0ebbe855a46fb2bb956ea1e06e8cf05d.jpg
1699 ms
like.php
92 ms
plusone.js
64 ms
ga.js
33 ms
133726
237 ms
likebox.php
169 ms
like.php
77 ms
__utm.gif
37 ms
cb=gapi.loaded_0
49 ms
cb=gapi.loaded_1
46 ms
fastbutton
117 ms
vpc6VNjRPXV.js
515 ms
LVx-xkvaJ0b.png
385 ms
xml.php
1602 ms
B_7f6e824dac58e306b00a5dfab42950fd.jpg
1531 ms
B_e37688c62399249e0abe5f51b03ded0c.jpg
1726 ms
B_824511d5f51ab3661a80192bedbdc866.jpg
1781 ms
postmessageRelay
87 ms
n7IAcY2jJIh.css
316 ms
n--mLoVmLJM.css
317 ms
_rx8naC75Dy.js
445 ms
x5F9OMjKyLw.js
462 ms
ICDbTSzjQEg.js
357 ms
TTCre3391I0.js
655 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
33 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
52 ms
api.js
39 ms
core:rpc:shindig.random:shindig.sha1.js
41 ms
2536007149-postmessagerelay.js
34 ms
footer_line.jpg
1527 ms
logo_small.png
1583 ms
icon_twitter.png
1604 ms
icon_facebook.png
1708 ms
icon_rss.png
1719 ms
bg_btn3.png
1641 ms
bg_li.png
1703 ms
ui-bg_flat_75_ffffff_40x100.png
1717 ms
1979639_754212447929931_2115656359_n.png
691 ms
537214_580834981934346_1463557759_n.png
782 ms
12734049_1127791043911562_1961487052115015142_n.jpg
906 ms
11813529_1105925306103100_7810312553879751301_n.jpg
949 ms
12744184_983459511722682_2202733452719782830_n.jpg
913 ms
11541929_1656193337944448_2341587424194053225_n.jpg
1075 ms
12243520_10200907920975521_2818787992440620177_n.jpg
970 ms
531883_451052524960121_452780109_n.jpg
916 ms
12118795_913874601983014_2474767752376675990_n.jpg
972 ms
11219011_1609973982602710_6800961495981457789_n.jpg
979 ms
12038330_137390419944590_1339853140795556638_n.jpg
1025 ms
11066516_10203861347362526_8897985995321637653_n.jpg
1015 ms
12744412_1340442899315052_8422534509665720439_n.jpg
1037 ms
155757_1229497195685_104752_n.jpg
1041 ms
12705740_220659468281406_6900001318471275790_n.jpg
1047 ms
wL6VQj7Ab77.png
70 ms
s7jcwEQH7Sx.png
69 ms
I6-MnjEovm5.js
70 ms
vlXaquuXMrr.js
135 ms
gepi.bg accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
gepi.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
gepi.bg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
BG
EN
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.
gepi.bg
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: