35.9 sec in total
850 ms
17.9 sec
17.1 sec
Welcome to eventim.bg homepage info - get ready to check EVENTIM best content for Bulgaria right away, or after learning these important things about eventim.bg
EVENTIM - online ticket shop
Visit eventim.bgWe analyzed Eventim.bg page load time and found that the first response time was 850 ms and then it took 35 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
eventim.bg performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value12.1 s
0/100
25%
Value9.7 s
10/100
10%
Value1,640 ms
12/100
30%
Value0.033
100/100
15%
Value17.0 s
5/100
10%
850 ms
808 ms
1284 ms
1581 ms
1166 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Eventim.bg, 91% (63 requests) were made to Bg.content.eventim.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Bg.content.eventim.com.
Page size can be reduced by 907.7 kB (35%)
2.6 MB
1.7 MB
In fact, the total size of Eventim.bg main page is 2.6 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 100.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 100.0 kB or 83% of the original size.
Potential reduce by 136.2 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. EVENTIM images are well optimized though.
Potential reduce by 317.1 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 317.1 kB or 63% of the original size.
Potential reduce by 354.4 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. Eventim.bg needs all CSS files to be minified and compressed as it can save up to 354.4 kB or 82% of the original size.
We found no issues to fix!
66
66
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EVENTIM. According to our analytics all requests are already optimized.
eventim.bg
850 ms
808 ms
css
1284 ms
responsive.css
1581 ms
jquery.min.js
1166 ms
api.js
1241 ms
laga_350_462.jpg
1425 ms
gi6c_350_226.jpg
1129 ms
28ph_350_226.jpg
936 ms
bj06_350_462.jpg
972 ms
2sft_350_226.jpg
1028 ms
npj2_350_226.jpg
1026 ms
mj4v_350_226.jpg
863 ms
zpgr_350_226.jpg
816 ms
ud7z_350_226.jpg
862 ms
udmn_170_226.jpg
641 ms
126g_170_226.jpg
916 ms
ne6i_350_226.jpg
917 ms
1fup_350_226.jpg
670 ms
5ldv_350_462.jpg
1030 ms
qbjc_350_226.jpg
1029 ms
pvlk_350_226.jpg
1008 ms
uz5e_140_186.jpg
1005 ms
bht7_140_186.jpg
1027 ms
x4k8_140_186.jpg
833 ms
4tvx_140_186.jpg
832 ms
ed76_140_186.jpg
834 ms
msf3_140_186.jpg
833 ms
7vdm_140_186.jpg
831 ms
4r28_140_186.jpg
832 ms
zd28_140_186.jpg
943 ms
mdq4_140_186.jpg
943 ms
75pu_140_186.jpg
943 ms
puru_140_186.jpg
943 ms
g48q_140_186.jpg
943 ms
2iyl_140_186.jpg
709 ms
p42d_140_186.jpg
708 ms
o07t_140_186.jpg
708 ms
yaz5_140_186.jpg
709 ms
qr5d_140_186.jpg
798 ms
8n27_140_186.jpg
708 ms
bpkr_140_186.jpg
797 ms
vgjb_140_186.jpg
760 ms
ym9q_140_186.jpg
750 ms
mmyu_140_186.jpg
714 ms
j7bl_140_186.jpg
660 ms
aor7_140_186.jpg
659 ms
tolk_140_186.jpg
658 ms
zspf_140_186.jpg
662 ms
6aos_320_206.jpg
663 ms
akaa_320_206.jpg
661 ms
rvk7_320_206.jpg
630 ms
e6e2_180_220.jpg
386 ms
31pn_180_220.jpg
386 ms
aapj_180_220.jpg
520 ms
bx0c_180_220.jpg
519 ms
o1uy_180_220.jpg
500 ms
ijlc_100_120.jpg
499 ms
mono-dhimahi-logo.png
532 ms
responsive_logo.png
1425 ms
price-leaf.png
1313 ms
illustrated-bg.png
1313 ms
yellow-arrow-right.png
1313 ms
oet-responsive.woff
360 ms
yellow-arrow-down-right.png
2105 ms
menu-bg-alt.png
1293 ms
newsletter-bottom.png
1292 ms
newsletter-top.png
1291 ms
recaptcha__ca.js
692 ms
eventim.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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eventim.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Page has valid source maps
eventim.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 Eventim.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 Eventim.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.
eventim.bg
Open Graph description is not detected on the main page of EVENTIM. 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: