5.8 sec in total
455 ms
5.1 sec
260 ms
Welcome to expert.bg homepage info - get ready to check Expert best content for Bulgaria right away, or after learning these important things about expert.bg
Бизнес, икономика, финанси от България и света | Expert.bg
Visit expert.bgWe analyzed Expert.bg page load time and found that the first response time was 455 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
expert.bg performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value6.8 s
7/100
25%
Value14.0 s
1/100
10%
Value2,390 ms
5/100
30%
Value0.294
41/100
15%
Value17.5 s
4/100
10%
455 ms
623 ms
215 ms
324 ms
331 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 17% of them (16 requests) were addressed to the original Expert.bg, 24% (23 requests) were made to Cdn.actualno.eu and 12% (11 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source A.actualno.com.
Page size can be reduced by 246.2 kB (26%)
963.6 kB
717.4 kB
In fact, the total size of Expert.bg main page is 963.6 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. 70% of websites need less resources to load. Javascripts take 633.8 kB which makes up the majority of the site volume.
Potential reduce by 158.1 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 44.9 kB, which is 24% 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 158.1 kB or 85% of the original size.
Potential reduce by 5.7 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. Expert images are well optimized though.
Potential reduce by 81.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 81.2 kB or 13% of the original size.
Potential reduce by 1.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. Expert.bg needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 11% of the original size.
Number of requests can be reduced by 47 (54%)
87
40
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Expert. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
expert.bg
455 ms
www.expert.bg
623 ms
NotoSans.css
215 ms
flexboxgrid.css
324 ms
style.css
331 ms
slick.css
334 ms
detect.min.js
35 ms
sp-push-worker.js
338 ms
gpt.js
210 ms
pb.js
550 ms
ado.js
1116 ms
dab.js
621 ms
master.js
630 ms
adsbygoogle.js
381 ms
jquery-1.11.0.min.js
361 ms
lazysizes.min.js
359 ms
slick.js
359 ms
pubads_impl.js
10 ms
128945922
77 ms
ad.js
114 ms
gtm.js
101 ms
AGSKWxWeuJokCIgR-E696iVE6tImhA83jmmgPRpbjERit_d4NG3N1zUJFCZ5zhSaGeQlRfmFa9jmwHZteSjY5cvrvsI=
70 ms
logo.png
137 ms
ns1_logo.svg
133 ms
bnb-logo.jpg
137 ms
arrow-down.svg
135 ms
show_ads_impl.js
296 ms
extra=;
860 ms
extra=;
849 ms
extra=;
870 ms
inspiro-icon.ttf
232 ms
js
46 ms
analytics.js
17 ms
icomoon.ttf
120 ms
extra=;
821 ms
billboard_v2_gao_lib.js
123 ms
collect
89 ms
collect
69 ms
future-creators.png
174 ms
extra=;
706 ms
xgemius.js
693 ms
096c9f2a263874bff961e86c2f717d87_2205549_920x517.webp
129 ms
0994385001666272331_2193229_920x517.webp
203 ms
0583313001714059768_2209986_920x517.webp
222 ms
0104545001647579522_2209829_920x517.webp
75 ms
0444953001688129095_2208070_920x517.webp
210 ms
0333731001714488727_2213548_920x517.webp
198 ms
0264404001701707557_2212433_920x517.webp
75 ms
0248449001704993279_2212245_920x517.webp
89 ms
6c4fecca7ead0a4b8a058dd4d23dfc57_2214500_395x301.webp
92 ms
0721072001698998807_2214063_395x301.webp
105 ms
zrt_lookup.html
63 ms
ads
495 ms
2c91f74cd4291dbf085bb8b304b9b744_2214806_395x301.webp
13 ms
320e00558307f704844a51a574628532_2215225_395x301.webp
18 ms
d9b0c0daa70ca1cc9fd74c05a9a68b69_2213844_395x301.webp
19 ms
0823047001564596427_2214002_395x301.webp
22 ms
0176304001649437555_2214233_395x301.webp
30 ms
0537219001714638089_2214056_395x301.webp
26 ms
0560119001545055259_2210355_920x517.webp
16 ms
0823148001684063599_2209094_920x517.webp
151 ms
0307226001687957485_2208591_920x517.webp
28 ms
0244481001712758856_2199546_920x517.webp
151 ms
0440936001712242499_2195279_920x517.webp
148 ms
0348215001711712195_2191231_920x517.webp
176 ms
dbcc00fac4ff9eeb4c5bceff4ee726d4_2216379_300x165.webp
29 ms
reactive_library.js
180 ms
fpdata.js
111 ms
lsget.html
892 ms
sodar
112 ms
8852706224605827758
418 ms
load_preloaded_resource.js
53 ms
icon.png
29 ms
abg_lite.js
281 ms
window_focus.js
280 ms
qs_click_protection.js
47 ms
ufs_web_display.js
34 ms
bbcd6bf18c20baa1b2adeb195de9b551.js
411 ms
fullscreen_api_adapter.js
395 ms
interstitial_ad_frame.js
405 ms
s
16 ms
one_click_handler_one_afma.js
397 ms
15461835243049902103
390 ms
feedback_grey600_24dp.png
394 ms
settings_grey600_24dp.png
395 ms
sodar2.js
385 ms
css
75 ms
runner.html
17 ms
aframe
92 ms
activeview
195 ms
feg8rL66UTsTrrlS9w_iUH8JqR_kCfLFdi2W6wljJCU.js
14 ms
sa30O7WeJNzu8x7oKdCcujxNj08-gvZudrea3FT7Uzc.js
58 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
166 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
167 ms
expert.bg accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
expert.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
expert.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
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 Expert.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 Expert.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.
expert.bg
Open Graph data is detected on the main page of Expert. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: