iec.bg Website Information
Daily Unique Visits: 895
Daily Page Views: 1,790
Income Per Day: $6
Estimated Value: $1,440
This website is located in Bulgaria and is using following IP address 195.191.148.59. See the complete list of popular websites hosted in Bulgaria.
iec.bg is registered under .BG top-level domain. Please check other sites in .BG zone.
Website iec.bg is using the following name servers:
- mail.iec.bg
- office.iec.bg
and is probably hosted by SuperHosting.BG Ltd.. See the full list of other websites hosted by SuperHosting.BG Ltd..
The highest website iec.bg position in Alexa rank database was 160243 and the lowest rank position was 999134. Current position of iec.bg in Alexa rank database is 801322.
Desktop speed score of iec.bg (83/100) is better than the results of 76.15% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of iec.bg (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.
Mobile speed score of iec.bg (58/100) is better than the results of 50.23% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
iec.bg Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
iec.bg whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
iec.bg server information
Servers Location
iec.bg desktop page speed rank
Last tested: 2019-10-28
iec.bg Desktop Speed Test Quick Summary
priority - 12Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
priority - 3Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
https://iec.bg/
https://iec.bg/index.php/en/
priority - 2Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 2Leverage 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:
https://js.hs-analytics.net/analytics/1572243600000/5597509.js (5 minutes)
https://js.usemessages.com/conversations-embed.js (10 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 0Reduce server response time
In our test, your server responded in 0.21 seconds.
priority - 0Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 563B (17% reduction).
priority - 0Minify 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 103B (22% reduction).
iec.bg Desktop Resource Breakdown
| Total Resources | 18 |
| Number of Hosts | 10 |
| Static Resources | 7 |
| JavaScript Resources | 6 |
| CSS Resources | 1 |
iec.bg mobile page speed rank
Last tested: 2019-11-21
iec.bg Mobile Speed Test Quick Summary
priority - 56Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
priority - 10Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
https://iec.bg/
https://iec.bg/index.php/en/
priority - 8Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 3Leverage 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:
https://js.hs-analytics.net/analytics/1574313000000/5597509.js (5 minutes)
https://js.usemessages.com/conversations-embed.js (10 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 1Reduce server response time
In our test, your server responded in 0.27 seconds.
priority - 0Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 565B (17% reduction).
priority - 0Minify 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 104B (22% reduction).
iec.bg Mobile Resource Breakdown
| Total Resources | 18 |
| Number of Hosts | 10 |
| Static Resources | 7 |
| JavaScript Resources | 6 |
| CSS Resources | 1 |
iec.bg mobile page usability
Last tested: 2019-11-21
iec.bg Mobile Usability Test Quick Summary
priority - 3Size 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 430 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:
<div class="float-left animated zoomIn">Calendar</div> falls outside the viewport.The element
<div class="float-left animated zoomIn">Our exhibitions</div> falls outside the viewport.The element
<div class="float-left animated zoomIn">Events & Mice</div> falls outside the viewport.The element
<div class="float-left animated zoomIn">Contacts</div> falls outside the viewport.priority - 1Size 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.
<a href="/index.php/stand-design" class="box-container">Stand design</a> is close to 1 other tap targets.<a class="cpnb-button cpnb-button-ok">Ok, I've understood!</a> is close to 1 other tap targets.iec.bg HTML validation
Warnings
Consider avoiding viewport values that prevent users from resizing documents.
"...HELD --> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no"/> <sty..."
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"... <section class="article-content clearfix" itemprop="articleBody"> ..." Line: 362 Column: 2 - 31
"...oter"> <section class="t3-copyright"> <di..."
Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.
"...ticle --> <article class="article" itemscope itemtype="http://schema.org/Article"> <meta..."
Errors
Bad value “0” for attribute “size” on element “input”: Zero is not a positive integer.
"....</label> <input name="searchword" id="mod-search-searchword" maxlength="200" class="form-control search-query" type="search" size="0" placeholder="търси..." /> <inp..."
Element “meta” is missing required attribute “content”.
"...Article"> <meta itemscope itemprop="mainEntityOfPage" itemType="https://schema.org/WebPage" itemid="https://google.com/article"/> <met..."
iec.bg similar domains
www.iec.net
www.iec.org
www.iec.info
www.iec.biz
www.iec.us
www.iec.mobi
www.ec.bg
www.iec.bg
www.uec.bg
www.iuec.bg
www.uiec.bg
www.jec.bg
www.ijec.bg
www.jiec.bg
www.kec.bg
www.ikec.bg
www.kiec.bg
www.oec.bg
www.ioec.bg
www.oiec.bg
www.ic.bg
www.iwc.bg
www.iewc.bg
www.iwec.bg
www.isc.bg
www.iesc.bg
www.isec.bg
www.idc.bg
www.iedc.bg
www.idec.bg
www.irc.bg
www.ierc.bg
www.irec.bg
www.ie.bg
www.iex.bg
www.iecx.bg
www.iexc.bg
www.ied.bg
www.iecd.bg
www.ief.bg
www.iecf.bg
www.iefc.bg
www.iev.bg
www.iecv.bg
www.ievc.bg
iec.bg Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
iec.bg TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.