7.5 sec in total
1.2 sec
5.8 sec
405 ms
Click here to check amazing EMAG content for Bulgaria. Otherwise, check out these important facts you probably never knew about emag.bg
Поръчай онлайн и с доставка до врата! Избери Електроника, големи и малки Електроуреди, IT, Продукти за дома, Градината, за Детето, Играчки, Книги и други.
Visit emag.bgWe analyzed Emag.bg page load time and found that the first response time was 1.2 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
emag.bg performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value6.2 s
11/100
25%
Value6.2 s
43/100
10%
Value430 ms
65/100
30%
Value0.002
100/100
15%
Value10.3 s
24/100
10%
1230 ms
492 ms
615 ms
370 ms
259 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 14% of them (16 requests) were addressed to the original Emag.bg, 61% (68 requests) were made to S1emagst.akamaized.net and 3% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source S1emagst.akamaized.net.
Page size can be reduced by 1.2 MB (58%)
2.2 MB
914.8 kB
In fact, the total size of Emag.bg main page is 2.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. 65% of websites need less resources to load. Javascripts take 833.7 kB which makes up the majority of the site volume.
Potential reduce by 302.7 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 67.9 kB, which is 19% 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 302.7 kB or 85% of the original size.
Potential reduce by 57.4 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. EMAG images are well optimized though.
Potential reduce by 600.5 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 600.5 kB or 72% of the original size.
Potential reduce by 283.2 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. Emag.bg needs all CSS files to be minified and compressed as it can save up to 283.2 kB or 83% of the original size.
Number of requests can be reduced by 27 (27%)
100
73
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EMAG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
www.emag.bg
1230 ms
homepage.css
492 ms
homepage.js
615 ms
custom-select.js
370 ms
emag_search_general.js
259 ms
068732dbb0d4a8cd8321735b6d1bf0222a6c2000
247 ms
emg-1.php
299 ms
api.js
39 ms
main.min.js
248 ms
main.min.js
252 ms
logger.min.js
252 ms
9508.png
95 ms
search_bubbles.png
111 ms
7017.png
94 ms
7173.png
92 ms
7030.png
160 ms
7020.png
275 ms
9738.png
110 ms
res_7a148ea3f0557cd203ad165dd033f0be_150x150_v60p.jpg
529 ms
res_087757118ce6f43c176b5f657e8dc862_150x150_1koa.jpg
528 ms
res_e17a8f8624905b63b5bd7a19a1b50018_150x150_46jo.jpg
156 ms
res_13cb7dd6e1ffbc29ace856ceb6eb1243_150x150_100_481c.jpg
528 ms
res_b683d1ebc136a62df030c56fbde76267_150x150_100_c3dm.jpg
528 ms
8946.jpg
192 ms
8947.jpg
192 ms
res_fa5b9c3203cecab3d49f98abf82aa17e_100x135_pgbm.jpg
586 ms
res_2d509db4625629a1d61a81f476dbf677_100x135_qaoi.jpg
213 ms
res_cda250d7c1c3da88ec3fa74cd87ffe17_100x135_h8t1.jpg
714 ms
res_57938ba9d15204c35da6cff80141045c_100x135_6ih8.jpg
586 ms
res_76b5a38a91ff46846c78ddfd7ff9e65e_100x135_uldr.jpg
915 ms
res_0445ad3f77c6d6bd9f453a5d80b95a25_100x135_5r1k.jpg
1025 ms
res_cdada0b9d1605f020fbd84c7450d6991_100x135_ec9d.jpg
922 ms
res_02b3b2ca05a8d21524823ffaa6084c14_100x135_ftgm.jpg
983 ms
res_bbefa9467a2c362e18c8ff81581ca683_100x135_uh9e.jpg
979 ms
res_4f27aff43414da4a6185e141ccf7f09c_100x135_kjg6.jpg
740 ms
banner_mobile_app.jpg
108 ms
8950.jpg
796 ms
res_fa114294f54b429dd721ec9da6e9c7f9_100x135_uh2a.jpg
825 ms
res_11a01e44bddcd345a2c1827f9a7d7d82_100x135_nilo.jpg
1219 ms
res_d0319e520bcbea8b21fa2dcb2c62a869_100x135_6eo0.jpg
941 ms
res_d97e87c19fdd2d25bde9b3d2722b7d4e_100x135_mogc.jpg
953 ms
res_682c6c6c6ef0dfb8072c2d9560ad581c_100x135_us4u.jpg
970 ms
res_dfc801ba437b6cbb2ad7ba84ac8a5eb1_100x135_2hq2.jpg
975 ms
res_9a7777a947a81459d57e792a4e18600d_100x135_ncc8.jpg
998 ms
res_0952e193efdce427c01a30203a85052b_100x135_dnvl.jpg
1012 ms
res_251ce2e3c00645e98aa48478324056ee_100x135_t2ch.jpg
1382 ms
res_255bc2ee769977e9ac5b3f794736239d_100x135_16aj.jpg
1009 ms
gtm.js
147 ms
opensans-regular-webfont-rocyplhu.ttf
182 ms
opensans-bold-webfont-rocyplhu.ttf
25 ms
layout-v11-light.ttf
25 ms
layout-v11-bold.ttf
50 ms
layout-v11-regular.ttf
42 ms
stymiemag-bold-webfont.woff
191 ms
gss55.ttf
40 ms
emg_icons_departments.1455276982.ttf
82 ms
res_bbefa9467a2c362e18c8ff81581ca683_150x150_q83b.jpg
1253 ms
res_2d509db4625629a1d61a81f476dbf677_150x150_ss30.jpg
904 ms
res_0445ad3f77c6d6bd9f453a5d80b95a25_150x150_5nc8.jpg
1247 ms
res_fa5b9c3203cecab3d49f98abf82aa17e_150x150_v8h5.jpg
1254 ms
res_fa114294f54b429dd721ec9da6e9c7f9_150x150_rif0.jpg
898 ms
res_682c6c6c6ef0dfb8072c2d9560ad581c_150x150_ui4r.jpg
931 ms
analytics.js
5 ms
fbevents.js
11 ms
res_4cb96569ae0f157f49bc33c45d02bcba_150x150_merd.jpg
1314 ms
126 ms
res_37beeab5b7562a436dded9f213e51645_150x150_v281.jpg
1396 ms
emg-2.php
109 ms
emg-4.js
181 ms
res_d8fa1a37a5746eda59683db2e88beddd_150x150_aje.jpg
1557 ms
res_d97e87c19fdd2d25bde9b3d2722b7d4e_150x150_sq86.jpg
1559 ms
10230.jpg
1132 ms
res_583b5261943a8ae3d92243590fcab0b6_100x135_v0o7.jpg
1513 ms
recaptcha__bg.js
114 ms
conversion_async.js
82 ms
ec.js
69 ms
site_ajax_rv
278 ms
ablogger.php
278 ms
ablogger.php
275 ms
collect
9 ms
collect
89 ms
res_0f1b73ee6524af0d9030e426d39c2d4e_100x135_o84g.jpg
1352 ms
res_3434b8bbfd057fe56f216fe10dfbe29b_100x135_do0t.jpg
1379 ms
res_39afd62d15aa4f8227e0e615ab793fe1_100x135_6gge.jpg
1486 ms
69 ms
res_9afad88ec003b185bb31ae61813747ba_100x135_lp4l.jpg
1686 ms
res_ea2874e4db712eb544ce3b8e5d6e7933_100x135_vps3.jpg
1270 ms
res_3802f1c0b76ce96c39e981ec5148c895_100x135_1v70.jpg
1637 ms
27 ms
ga-audiences
19 ms
res_147ad4ec45eaab2694975bab97183fcb_100x135_fd5r.jpg
1171 ms
res_1e4cf46d8aefac89a3081092f94bc0d3_100x135_htmt.jpg
1565 ms
res_3b06fe7b216dea28b3f31f128edbe511_100x135_q2q2.jpg
1479 ms
sprite_emag_no_lang.png
6 ms
8a5279ec96ac8c4427bcefe8fcd398a8.jpg
881 ms
gr_reco4-min.js
1015 ms
theme.css
816 ms
solr.js
841 ms
config.json
974 ms
ablogger.php
903 ms
plusone.js
423 ms
sdk.js
274 ms
7637f55ae18313c6d808f26bfd61e22b.js
377 ms
chartbeat.js
352 ms
ajax-loader.gif
107 ms
50 ms
ping
32 ms
42 ms
xd_arbiter.php
33 ms
xd_arbiter.php
48 ms
cb=gapi.loaded_0
17 ms
emag.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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
emag.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
emag.bg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Emag.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Emag.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.
emag.bg
Open Graph description is not detected on the main page of EMAG. 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: