5 sec in total
1.1 sec
3.6 sec
305 ms
Visit d21.bg now to see the best up-to-date D 21 content for Bulgaria and also check out these interesting facts you probably never knew about d21.bg
Visit d21.bgWe analyzed D21.bg page load time and found that the first response time was 1.1 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
d21.bg performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value8.8 s
1/100
25%
Value18.9 s
0/100
10%
Value910 ms
31/100
30%
Value0.033
100/100
15%
Value19.0 s
3/100
10%
1072 ms
136 ms
253 ms
262 ms
397 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 41% of them (59 requests) were addressed to the original D21.bg, 7% (10 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain D21.bg.
Page size can be reduced by 1.1 MB (56%)
1.9 MB
827.2 kB
In fact, the total size of D21.bg main page is 1.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 925.3 kB which makes up the majority of the site volume.
Potential reduce by 226.9 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 226.9 kB or 90% of the original size.
Potential reduce by 33.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. D 21 images are well optimized though.
Potential reduce by 681.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 681.5 kB or 74% of the original size.
Potential reduce by 129.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. D21.bg needs all CSS files to be minified and compressed as it can save up to 129.2 kB or 85% of the original size.
Number of requests can be reduced by 71 (56%)
127
56
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of D 21. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
d21.bg
1072 ms
lora.css
136 ms
greatVibes.css
253 ms
grid960.css
262 ms
style.css
397 ms
shareaholic.js
13 ms
style.css
272 ms
settings.css
264 ms
captions.css
280 ms
style.css
374 ms
prettyPhoto.css
391 ms
style.css
391 ms
widget.js
419 ms
jquery.js
603 ms
jquery-migrate.min.js
496 ms
jquery.themepunch.plugins.min.js
522 ms
jquery.themepunch.revolution.min.js
523 ms
jquery.prettyPhoto.js
526 ms
slides.min.jquery.js
540 ms
jquery.easing.1.3.js
616 ms
jquery.uniform.min.js
648 ms
tbUniform.js
646 ms
themeblossom.js
653 ms
wp-embed.min.js
669 ms
css
39 ms
css
15 ms
wp-emoji-release.min.js
332 ms
easy-table.css
332 ms
50e96a54dab199fb5541b70a7f497a1e.json
39 ms
hqdefault.jpg
69 ms
headerBckg.png
199 ms
dvijenie_logo14.png
197 ms
navigation-white.png
197 ms
shadow.png
200 ms
transparentB10.png
128 ms
divider2.png
195 ms
transparent.png
511 ms
shadowGradient.png
509 ms
contentShadow.png
509 ms
shadow940.png
509 ms
D21_logo_938x350.jpg
513 ms
transparentB45.png
510 ms
DSC6418_938x350.jpg
823 ms
photo_2-940x350.jpg
815 ms
Photo2-940x350.jpg
710 ms
video3-444x237.jpg
546 ms
video1-444x237.jpg
564 ms
video-444x237.jpg
700 ms
video3-147x102.jpg
667 ms
video1-147x102.jpg
692 ms
video-147x102.jpg
789 ms
hqdefault.jpg
196 ms
hqdefault.jpg
125 ms
hqdefault.jpg
124 ms
hqdefault.jpg
122 ms
horShadowInner.png
806 ms
sidebar.png
822 ms
navigation-blue.png
837 ms
shrMain.min.js
12 ms
4A-myfZX6oDr9CtSTkTGig.ttf
47 ms
rapsGf8n-DpRu9kcmAAciA.ttf
48 ms
all.js
43 ms
Danail_Georgiev-327x193.jpg
863 ms
paperClip.png
901 ms
IMG_6264-crop-147x102.jpg
902 ms
photo11-147x102.jpg
908 ms
photo_2-147x102.jpg
933 ms
player.png
937 ms
footer.png
998 ms
bottomLine.png
1017 ms
jquery.min.js
57 ms
analytics.js
69 ms
303 ms
pageview.gif
216 ms
xd_arbiter.php
39 ms
xd_arbiter.php
64 ms
play.png
570 ms
backToTop.png
583 ms
vglnk.js
19 ms
partners.js
579 ms
like_box.php
385 ms
pixel.gif
6 ms
pixel.gif
6 ms
410ucuAGgaJ.css
43 ms
tSbl8xBI27R.css
46 ms
q68gy-v_YMF.js
54 ms
FJmpeSpHpjS.js
68 ms
0wM5s1Khldu.js
67 ms
1bNoFZUdlYZ.js
67 ms
12219594_1224842550863157_7491759960762786060_n.jpg
108 ms
10615557_943126122368136_8463355193478227236_n.png
18 ms
1509852_10205711232321332_9117563182034885708_n.jpg
108 ms
18374_102994289728231_2715628_n.jpg
28 ms
1380091_166003663600560_24884542_n.jpg
21 ms
12729129_1011372982267641_6751966037741473738_n.jpg
87 ms
12316607_10208178988015153_6403539995280549616_n.jpg
23 ms
9201_1739318986282934_5970239377883215987_n.jpg
24 ms
1237846_701003066582699_793535585_n.jpg
26 ms
wL6VQj7Ab77.png
14 ms
s7jcwEQH7Sx.png
14 ms
ping
15 ms
sholic.js
58 ms
usermatch
209 ms
beacon.js
5 ms
domains
54 ms
cms-sh2c.html
66 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
6 ms
eexelate.js
27 ms
77 ms
ping_match.gif
8 ms
2964
29 ms
pixel
34 ms
ep
38 ms
rs
9 ms
128 ms
pixel
31 ms
ep
32 ms
match-result
40 ms
pixel
16 ms
cm
64 ms
usermatch
125 ms
net.php
16 ms
pixel
14 ms
generic
6 ms
generic
4 ms
pixel.gif
20 ms
pixel.gif
4 ms
xrefid.xgi
5 ms
pixel
25 ms
gr
70 ms
casale
63 ms
pm_match
74 ms
casale
73 ms
i.gif
122 ms
crum
201 ms
xrefid.xgi
26 ms
crum
242 ms
cfcm.ashx
12 ms
rum
226 ms
rum
229 ms
m
52 ms
crum
228 ms
crum
125 ms
d21.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
d21.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
d21.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
BG
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise D21.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 D21.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.
d21.bg
Open Graph description is not detected on the main page of D 21. 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: