dfz.bg website information.
dfz.bg domain name is registered by .BG top-level domain registry. See the other sites registred in .BG domain zone.
Following name servers are specified for dfz.bg domain:
- ns2.dfz.bg
- ns1.dfz.bg
and probably website dfz.bg is hosted by CLOUDFLARENET - Cloudflare, Inc., US web hosting company. Check the complete list of other most popular websites hosted by CLOUDFLARENET - Cloudflare, Inc., US hosting company.
According to Alexa traffic rank the highest website dfz.bg position was 34751 (in the world). The lowest Alexa rank position was 999769. Now website dfz.bg ranked in Alexa database as number 779638 (in the world).
Website dfz.bg Desktop speed measurement score (85/100) is better than the results of 80% of other sites and shows that the page is performing great on desktop computers.
dfz.bg Mobile usability score (62/100) is better than the results of 7.29% of other sites and shows that the page mobile usability is poor and can be improved.
Mobile speed measurement score of dfz.bg (79/100) is better than the results of 87.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Nov-26-2024 | 779,638 | -1,664 |
| Nov-25-2024 | 777,974 | -10,302 |
| Nov-24-2024 | 767,672 | -309 |
| Nov-23-2024 | 767,363 | 8,868 |
| Nov-22-2024 | 776,231 | 7,195 |
| Nov-21-2024 | 783,426 | -33,423 |
| Nov-20-2024 | 750,003 | 31,085 |
Advertisement
dfz.bg Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
dfz.bg whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
DOMAIN NAME: dfz.bg (dfz.bg)
registration status: busy, active
NAME SERVER INFORMATION:
ns1.dfz.bg 195.110.24.248
ns2.dfz.bg 195.110.25.248
ns3.dfz.bg 195.110.24.247
DNSSEC: inactive
According to REGULATION (EU) 2016/679 OF THE EUROPEAN PARLIAMENT AND
OF THE COUNCIL (GDPR) personal data is not published.
If you would like to contact the persons responsible for the domain
name, please, use the online WHOIS contact form from the "Info / Whois" menu
at www.register.bg.
dfz.bg server information
dfz.bg desktop page speed rank
Last tested: 2019-10-14
dfz.bg Desktop Speed Test Quick Summary
priority - 4 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Optimize CSS Delivery of the following:
http://dfz.bg/layout.css
http://dfz.bg/stylesheets/events_calendar.css
priority - 4 Reduce server response time
In our test, your server responded in 0.56 seconds.
There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 3 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 32.5KiB (39% reduction).
Compressing http://dfz.bg/images/new_images/header_img_bg.jpg could save 5.6KiB (19% reduction).
Compressing http://dfz.bg/assets/4351/logo_u_f.jpg could save 1.9KiB (25% reduction).
Compressing http://dfz.bg/images/new_images/rss-dfz.gif could save 496B (49% reduction).
Compressing http://dfz.bg/images/new_images/fav-dfz-3.gif could save 480B (47% reduction).
Compressing http://dfz.bg/images/new_images/print-dfz.gif could save 444B (43% reduction).
Compressing http://dfz.bg/images/new_images/email-dfz.gif could save 189B (33% reduction).
priority - 2 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://dfz.bg/images/new_images/header_img_bg.jpg (1 second)
http://dfz.bg/images/new_images/search-btn.gif (1 second)
http://dfz.bg/images/new_images/stroke_down.gif (1 second)
http://www.google-analytics.com/ga.js (2 hours)
priority - 1 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 11KiB (70% reduction).
Compressing http://dfz.bg/site.js could save 2.4KiB (64% reduction).
Compressing http://dfz.bg/javascripts/events_calendar.js could save 2.2KiB (68% reduction).
Compressing http://dfz.bg/styleswitcher.js could save 1.3KiB (67% reduction).
priority - 1 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 9.5KiB (18% reduction).
Minifying http://dfz.bg/site.js could save 1.2KiB (34% reduction).
Minifying http://dfz.bg/javascripts/lbox.js could save 1KiB (15% reduction).
Minifying http://dfz.bg/javascripts/events_calendar.js could save 986B (30% reduction).
Minifying http://dfz.bg/styleswitcher.js could save 354B (19% reduction).
priority - 0 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 2.1KiB (27% reduction).
Minifying http://dfz.bg/layout2.css could save 381B (32% reduction) after compression.
Minifying http://dfz.bg/layout3.css could save 350B (31% reduction) after compression.
dfz.bg Desktop Resources
| Total Resources | 35 |
| Number of Hosts | 4 |
| Static Resources | 9 |
| JavaScript Resources | 8 |
| CSS Resources | 6 |
dfz.bg Desktop Resource Breakdown
dfz.bg mobile page speed rank
Last tested: 2019-09-07
dfz.bg Mobile Speed Test Quick Summary
priority - 16 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Optimize CSS Delivery of the following:
http://dfz.bg/layout.css
http://dfz.bg/stylesheets/events_calendar.css
priority - 5 Reduce server response time
In our test, your server responded in 0.54 seconds.
There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 1 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 11KiB (70% reduction).
Compressing http://dfz.bg/site.js could save 2.4KiB (64% reduction).
Compressing http://dfz.bg/javascripts/events_calendar.js could save 2.2KiB (68% reduction).
Compressing http://dfz.bg/styleswitcher.js could save 1.3KiB (67% reduction).
priority - 1 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 9.5KiB (18% reduction).
Minifying http://dfz.bg/site.js could save 1.2KiB (34% reduction).
Minifying http://dfz.bg/javascripts/lbox.js could save 1KiB (15% reduction).
Minifying http://dfz.bg/javascripts/events_calendar.js could save 986B (30% reduction).
Minifying http://dfz.bg/styleswitcher.js could save 354B (19% reduction).
priority - 1 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 9.1KiB (22% reduction).
Compressing http://dfz.bg/assets/4351/logo_u_f.jpg could save 1.9KiB (25% reduction).
Compressing http://dfz.bg/images/new_images/rss-dfz.gif could save 496B (49% reduction).
Compressing http://dfz.bg/images/new_images/fav-dfz-3.gif could save 480B (47% reduction).
Compressing http://dfz.bg/images/new_images/print-dfz.gif could save 444B (43% reduction).
Compressing http://dfz.bg/images/new_images/email-dfz.gif could save 189B (33% reduction).
priority - 1 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
priority - 0 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 2.1KiB (27% reduction).
Minifying http://dfz.bg/layout2.css could save 381B (32% reduction) after compression.
Minifying http://dfz.bg/layout3.css could save 350B (31% reduction) after compression.
dfz.bg Mobile Resources
| Total Resources | 35 |
| Number of Hosts | 4 |
| Static Resources | 5 |
| JavaScript Resources | 8 |
| CSS Resources | 6 |
dfz.bg Mobile Resource Breakdown
dfz.bg mobile page usability
Last tested: 2019-09-07
dfz.bg Mobile Usability Test Quick Summary
priority - 40 Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
Този сайт изпо…имално за Вас. renders only 6 pixels tall (16 CSS pixels).Прочети още renders only 6 pixels tall (16 CSS pixels).Разбирам renders only 5 pixels tall (14 CSS pixels).A renders only 4 pixels tall (10 CSS pixels).Карта на сайта and 3 others render only 5 pixels tall (13 CSS pixels).A renders only 6 pixels tall (16 CSS pixels).Начало renders only 5 pixels tall (12 CSS pixels).Достъп до обще…ена информация and 9 others render only 5 pixels tall (12 CSS pixels).ИНФОРМАЦИОНЕН ЦЕНТЪР renders only 5 pixels tall (13 CSS pixels).До 25 септемвр…ската програма and 6 others render only 5 pixels tall (14 CSS pixels).София 1040, "Христо Ботев" 55 and 3 others render only 5 pixels tall (13 CSS pixels).minister@mzh.government.bg and 2 others render only 5 pixels tall (13 CSS pixels).Сигнали за изм…ионни практики and 1 others render only 5 pixels tall (13 CSS pixels).SIGNALI@DFZ.BG and 1 others render only 7 pixels tall (18 CSS pixels).Декларирани ка…ектни плащания and 4 others render only 5 pixels tall (13 CSS pixels).Начало renders only 5 pixels tall (12 CSS pixels).Новини renders only 5 pixels tall (14 CSS pixels).Изпълнителният…и в целия ЕС. and 6 others render only 5 pixels tall (13 CSS pixels).Публикувано в and 9 others render only 4 pixels tall (11 CSS pixels).Прочети цялата новина and 9 others render only 4 pixels tall (11 CSS pixels).заповед renders only 4 pixels tall (11 CSS pixels).Предишна renders only 5 pixels tall (13 CSS pixels).1 renders only 5 pixels tall (13 CSS pixels).Следваща and 5 others render only 5 pixels tall (13 CSS pixels).Програма за ра…йони 2014-2020 and 7 others render only 5 pixels tall (13 CSS pixels).ТЕКУЩИ ПРИЕМИ and 1 others render only 5 pixels tall (12 CSS pixels).< Aug renders only 4 pixels tall (10 CSS pixels).September renders only 4 pixels tall (11 CSS pixels).Oct > renders only 4 pixels tall (10 CSS pixels).Su and 6 others render only 3 pixels tall (9 CSS pixels).14 and 7 others render only 4 pixels tall (10 CSS pixels).10 and 19 others render only 4 pixels tall (10 CSS pixels).7 renders only 4 pixels tall (10 CSS pixels).30 renders only 4 pixels tall (10 CSS pixels).1 and 3 others render only 4 pixels tall (10 CSS pixels).5 renders only 4 pixels tall (10 CSS pixels).Регистър на по…редходните две and 2 others render only 5 pixels tall (12 CSS pixels).© 2009 - 2018…ights reserved and 2 others render only 4 pixels tall (11 CSS pixels).priority - 11 Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<input id="q" type="text" name="q" class="search"> is close to 1 other tap targets.<input type="submit" class="button_search"> is close to 2 other tap targets.<a class="first_a">A</a> is close to 3 other tap targets.<a class="second_a">A</a> and 2 others are close to other tap targets.<a class="third_a">A</a> is close to 4 other tap targets.<a href="/bg/">Начало</a> and 10 others are close to other tap targets.<a href="http://www.dfz…/bg/inf-center" class="signali">ИНФОРМАЦИОНЕН ЦЕНТЪР</a> is close to 1 other tap targets.<a href="mailto:ministe….government.bg" class="nodecoration">minister@mzh.government.bg</a> and 1 others are close to other tap targets.<a href="/bg/prescentar/novini/-25---/">До 25 септемвр…ската програма</a> and 4 others are close to other tap targets.<a href="/bg/prescentar/novini/">Новини</a> and 7 others are close to other tap targets.<a href="/assets/16698/gaziol.JPG"></a> is close to 1 other tap targets.<a href="/bg/prescentar/novini/2">2</a> and 4 others are close to other tap targets.<a href="http://www.dfz.bg/zCalc.htm"></a> and 5 others are close to other tap targets.<a href="javascript: void(0);" class="main_link">Директни плащания 2007-2013</a> and 1 others are close to other tap targets.<a href="http://www.dfz…kushti-priemi/">ТЕКУЩИ ПРИЕМИ</a> and 2 others are close to other tap targets.<a href="/calendar/2019/8">< Aug</a> is close to 1 other tap targets.<a href="/calendar/2019/10">Oct ></a> is close to 1 other tap targets.<a href="/events/2019/9/30">30</a> is close to 1 other tap targets.priority - 10 Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
Configure a viewport for this page.
priority - 3 Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 981 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<div class="footer">© 2009 - 2018…agic Solutions</div> falls outside the viewport.dfz.bg similar domains
www.dfz.net
www.dfz.org
www.dfz.info
www.dfz.biz
www.dfz.us
www.dfz.mobi
www.fz.bg
www.dfz.bg
www.xfz.bg
www.dxfz.bg
www.xdfz.bg
www.sfz.bg
www.dsfz.bg
www.sdfz.bg
www.efz.bg
www.defz.bg
www.edfz.bg
www.rfz.bg
www.drfz.bg
www.rdfz.bg
www.ffz.bg
www.dffz.bg
www.fdfz.bg
www.cfz.bg
www.dcfz.bg
www.cdfz.bg
www.dz.bg
www.dcz.bg
www.dfcz.bg
www.ddz.bg
www.dfdz.bg
www.ddfz.bg
www.drz.bg
www.dfrz.bg
www.dtz.bg
www.dftz.bg
www.dtfz.bg
www.dgz.bg
www.dfgz.bg
www.dgfz.bg
www.dvz.bg
www.dfvz.bg
www.dvfz.bg
www.df.bg
www.dfx.bg
www.dfzx.bg
www.dfxz.bg
www.dfs.bg
www.dfzs.bg
www.dfsz.bg
www.dfa.bg
www.dfza.bg
www.dfaz.bg
dfz.bg Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
dfz.bg TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.