omda.bg Website Information

Daily Unique Visits: 2,230

Daily Page Views: 6,690

Income Per Day: $20

Estimated Value: $7,200

omda.bg is registered under .BG top-level domain. Please check other sites in .BG zone.

No name server records were found.

and is probably hosted by SuperHosting.BG Ltd.. See the full list of other websites hosted by SuperHosting.BG Ltd..

The highest website omda.bg position in Alexa rank database was 24826 and the lowest rank position was 999909. Current position of omda.bg in Alexa rank database is 482418.

Desktop speed score of omda.bg (61/100) is better than the results of 37.05% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of omda.bg (56/100) is better than the results of 0.56% of other sites and means that the page is not mobile-friendly.

Mobile speed score of omda.bg (62/100) is better than the results of 59.44% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

omda.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.

omda.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.

Query limit exceeded, try again later.

omda.bg server information

Servers Location

omda.bg desktop page speed rank

Last tested: 2017-05-18

Desktop Speed Bad

61/100

omda.bg Desktop Speed Test Quick Summary

priority - 45Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 438.1KiB (90% reduction).

Compressing and resizing http://www.omda.bg/uploaded_files/images/polska-skakavitsa-2.jpg could save 427.2KiB (92% reduction).
Compressing and resizing http://www.omda.bg/styles/buttons/youtube.png could save 4.1KiB (63% reduction).
Compressing and resizing http://www.omda.bg/styles/buttons/twitter.png could save 3.4KiB (61% reduction).
Compressing and resizing http://www.omda.bg/styles/buttons/facebook.png could save 2.9KiB (60% reduction).
Compressing http://www.omda.bg/styles/images/omda_logo.png could save 530B (11% reduction).

priority - 15Leverage 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://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
http://www.omda.bg/common_files/java_scripts/jquery-1.8.2.min.js (4 hours)
http://www.omda.bg/common_files/java_scripts/jquery.colorbox-min.js (4 hours)
http://www.omda.bg/common_files/java_scripts/jquery.pajinate.min.js (4 hours)
http://www.omda.bg/common_files/java_scripts/main.js (4 hours)
http://www.omda.bg/common_files/java_scripts/menu.js (4 hours)
http://www.omda.bg/events/calendar.css (4 hours)
http://www.omda.bg/gallery/functions/graphics/loader.white.gif (4 hours)
http://www.omda.bg/gallery/functions/graphics/outlines/rounded-white.png (4 hours)
http://www.omda.bg/gallery/functions/highslide-with-html.js (4 hours)
http://www.omda.bg/gallery/functions/highslide.css (4 hours)
http://www.omda.bg/styles/buttons/eye.jpg (4 hours)
http://www.omda.bg/styles/buttons/facebook.png (4 hours)
http://www.omda.bg/styles/buttons/netaid.jpg (4 hours)
http://www.omda.bg/styles/buttons/twitter.png (4 hours)
http://www.omda.bg/styles/buttons/youtube.png (4 hours)
http://www.omda.bg/styles/colorbox.css (4 hours)
http://www.omda.bg/styles/emojione.css (4 hours)
http://www.omda.bg/styles/images/loop.gif (4 hours)
http://www.omda.bg/styles/images/omda_bul.gif (4 hours)
http://www.omda.bg/styles/images/omda_logo.png (4 hours)
http://www.omda.bg/styles/images/sep.gif (4 hours)
http://www.omda.bg/styles/images/sep_bottom.gif (4 hours)
http://www.omda.bg/styles/layout.css (4 hours)
http://www.omda.bg/styles/menu.css (4 hours)
http://www.omda.bg/styles/print.css (4 hours)
http://www.omda.bg/uploaded_files/image/bgs_header/red.gif (4 hours)
http://www.omda.bg/uploaded_files/images/polska-skakavitsa-2.jpg (4 hours)

priority - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 6 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.omda.bg/common_files/java_scripts/main.js
http://www.omda.bg/common_files/java_scripts/menu.js
http://www.omda.bg/common_files/java_scripts/jquery-1.8.2.min.js
http://www.omda.bg/common_files/java_scripts/jquery.pajinate.min.js
http://www.omda.bg/common_files/java_scripts/jquery.colorbox-min.js
http://www.omda.bg/gallery/functions/highslide-with-html.js

Optimize CSS Delivery of the following:

http://www.omda.bg/styles/layout.css
http://www.omda.bg/styles/menu.css
http://www.omda.bg/events/calendar.css
http://www.omda.bg/gallery/functions/highslide.css
http://www.omda.bg/styles/colorbox.css
http://www.omda.bg/styles/emojione.css

priority - 1Reduce server response time

priority - 1Minify 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 6.2KiB (25% reduction).

Minifying http://www.omda.bg/gallery/functions/highslide-with-html.js could save 3.7KiB (20% reduction) after compression.
Minifying http://www.omda.bg/common_files/java_scripts/menu.js could save 1.3KiB (41% reduction) after compression.
Minifying http://www.omda.bg/common_files/java_scripts/main.js could save 1.2KiB (45% reduction) after compression.

priority - 0Minify 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 1.7KiB (23% reduction).

Minifying http://www.omda.bg/styles/layout.css could save 1,003B (25% reduction) after compression.
Minifying http://www.omda.bg/gallery/functions/highslide.css could save 726B (21% reduction) after compression.

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 1.1KiB (15% reduction).

Minifying http://www.omda.bg/ could save 1.1KiB (15% reduction) after compression.

omda.bg Desktop Resource Breakdown

Total Resources	42
Number of Hosts	9
Static Resources	34
JavaScript Resources	12
CSS Resources	7

omda.bg mobile page speed rank

Last tested: 2017-05-18

Mobile Speed Bad

62/100

omda.bg Mobile Speed Test Quick Summary

priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 8 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Use asynchronous versions of the following scripts:

http://pagead2.googlesyndication.com/pagead/show_ads.js

Optimize CSS Delivery of the following:

priority - 22Leverage 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 - 9Reduce server response time

priority - 1Minify 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 6.2KiB (25% reduction).

priority - 0Minify 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 1.7KiB (23% reduction).

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 1.1KiB (15% reduction).

Minifying http://www.omda.bg/ could save 1.1KiB (15% reduction) after compression.

priority - 0Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 530B (11% reduction).

Compressing http://www.omda.bg/styles/images/omda_logo.png could save 530B (11% reduction).

omda.bg Mobile Resource Breakdown

Total Resources	42
Number of Hosts	9
Static Resources	34
JavaScript Resources	12
CSS Resources	7

omda.bg mobile page usability

Last tested: 2017-05-18

Mobile Usability Bad

56/100

omda.bg Mobile Usability Test Quick Summary

priority - 37Use 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.

BG renders only 5 pixels tall (12 CSS pixels).

| and 1 others render only 5 pixels tall (12 CSS pixels).

календар and 1 others render only 5 pixels tall (12 CSS pixels).
: renders only 5 pixels tall (12 CSS pixels).

ОРКЕСТЪР ОМДА renders only 4 pixels tall (11 CSS pixels).

ХРИСТОМАТИЯ ОМДА and 6 others render only 4 pixels tall (11 CSS pixels).

Карта на сайта and 4 others render only 5 pixels tall (12 CSS pixels).

| and 3 others render only 5 pixels tall (13 CSS pixels).

19 май 2017г. renders only 7 pixels tall (19 CSS pixels).

Св. свещеномъч…а конф. на СДС renders only 5 pixels tall (13 CSS pixels).

® снимка Севдалин Атанасов renders only 5 pixels tall (13 CSS pixels).

Полска Скакави…а от Кюстендил renders only 4 pixels tall (11 CSS pixels).

ПОСЛЕДНИ СТАТИИ renders only 5 pixels tall (12 CSS pixels).

Христоматия Омда and 8 others render only 5 pixels tall (12 CSS pixels).

Световно влиян…българската... and 31 others render only 5 pixels tall (13 CSS pixels).

ХРИСТОМАТИЯ ОМДА and 7 others render only 4 pixels tall (11 CSS pixels).

Строителството на социализма and 34 others render only 3 pixels tall (9 CSS pixels).

Революшън Технолоджис. renders only 3 pixels tall (9 CSS pixels).

Page generated….0200 seconds. renders only 3 pixels tall (9 CSS pixels).

priority - 25Size 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.

The tap target <a href="http://www.omd…enu=1&IDLang=2">en</a> is close to 1 other tap targets.

The tap target <a href="http://www.omd…enu=1&IDLang=1" class="menuLink">Оркестър Омда</a> is close to 2 other tap targets.

The tap target <a href="http://www.omd…u=102&IDLang=1" class="menuLink">Христоматия Омда</a> and 2 others are close to other tap targets.

The tap target <a href="http://www.omd…p.php?IDMenu=3">Карта на сайта</a> and 4 others are close to other tap targets.

The tap target <input type="image" class="searchButtonIMG"> is close to 1 other tap targets.

The tap target <a href="http://www.omd…IDArticle=6095">БЛАГОДАРЯ ТИ, КРИСТИЯНЕ!</a> and 45 others are close to other tap targets.

The tap target <a href="http://www.omd…enu=1&IDLang=1" class="bottom_menu">Оркестър Омда</a> and 7 others are close to other tap targets.

The tap target <a href="http://www.omd…p.php?IDMenu=3">Карта на сайта</a> and 42 others are close to other tap targets.

The tap target <a href="http://www.bigeye.com/"></a> and 3 others are close to other tap targets.

priority - 14Size 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 1,202 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="http://www.omd…u=490&IDLang=1">Календар</a> falls outside the viewport.
The element <a href="http://www.omd…enu=2&IDLang=1">Контакти</a> falls outside the viewport.
The element <a href="http://www.omd…u=114&IDLang=1" class="menuLink">Архив Омда</a> falls outside the viewport.
The element <ul>Карта на сайта…prehod.omda.bg</ul> falls outside the viewport.
The element <a href="http://www.omd…h=05&Year=2017">19 май 2017г.</a> falls outside the viewport.
The element <p>Св. свещеномъч…а конф. на СДС</p> falls outside the viewport.
The element <input type="text" name="q" class="searchField"> falls outside the viewport.
The element <input type="image" class="searchButtonIMG"> falls outside the viewport.
The element <p></p> falls outside the viewport.
The element <p>® снимка Севдалин Атанасов</p> falls outside the viewport.
The element <p>Полска Скакави…а от Кюстендил</p> falls outside the viewport.
The element <iframe id="aswift_0" name="aswift_0"> falls outside the viewport.
The element <img src="http://www.omd…ons/netaid.jpg"> falls outside the viewport.
The element <tr>Оркестър Омда…Сергия</tr> falls outside the viewport.
The element <a href="http://www.omd…u=114&IDLang=1" class="bottom_menu">Архив Омда</a> falls outside the viewport.
The element <li class="sub_menus_item">Склад</li> falls outside the viewport.
The element <a href="http://www.omd…u=242&IDLang=1">Студентски форум</a> falls outside the viewport.
The element <a href="http://www.omd…u=153&IDLang=1">Филателни страници</a> falls outside the viewport.
The element <a href="http://www.omd…u=542&IDLang=1">Новини в буркани</a> falls outside the viewport.
The element <a href="http://www.omd…u=797&IDLang=1">Футбол: Франция '98</a> falls outside the viewport.
The element <img src="http://www.omd…uttons/eye.jpg"> falls outside the viewport.
The element <img src="http://www.omd…s/facebook.png"> falls outside the viewport.
The element <img src="http://www.omd…ns/twitter.png"> falls outside the viewport.
The element <img src="http://www.omd…ns/youtube.png"> falls outside the viewport.
The element <div> falls outside the viewport.

priority - 10Configure 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.

omda.bg HTML validation

Errors

Obsolete doctype. Expected “<!DOCTYPE html>”.

Line: 2 Column: 1 - 56
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html..."

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

Line: 11 Column: 1 - 51
"...utf-8" /> <meta http-equiv="Content-Language" content="bg" /> <meta..."

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 18 Column: 1 - 52
"...="all" /> <meta http-equiv="X-UA-Compatible" content="IE=9" /> <meta..."

Bad value “description” for attribute “http-equiv” on element “meta”.

Attribute “name” not allowed on element “meta” at this point.

Line: 19 Column: 1 - 218
"..."IE=9" /> <meta http-equiv = "description" content = "Енциклопедични статии и подбрани текстове за народа, историята, земята, етнографията, фолклора и кухнята на българите. Животоописания на съвременици." name = "description" /> <meta..." Line: 20 Column: 1 - 146
"...ption" /> <meta http-equiv = "keywords" content = "Омда, България, народ, история, етнография, фолклор, природа, животоописания, кухня" name = "keywords" /> <link..."

Bad value “keywords” for attribute “http-equiv” on element “meta”.

Line: 20 Column: 1 - 146
"...ption" /> <meta http-equiv = "keywords" content = "Омда, България, народ, история, етнография, фолклор, природа, животоописания, кухня" name = "keywords" /> <link..."

Element “input” is missing required attribute “alt”.

Line: 232 Column: 147 - 262
"...);" /> <input class = "searchButtonIMG" type="image" src="http://www.omda.bg/styles/images/loop.gif" style="border:none" /> </di..."

The “center” element is obsolete. Use CSS instead.

Line: 261 Column: 57 - 64
"...op: 0px;"><center> <s..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 274 Column: 54 - 135
"..."_blank" ><img src ="http://www.omda.bg/styles/buttons/netaid.jpg" style = "border:none;" /></a> ..." Line: 439 Column: 65 - 124
"... "_blank"><img src="http://www.omda.bg/styles/buttons/facebook.png" /></a> ..." Line: 440 Column: 87 - 145
"..."_blank" ><img src="http://www.omda.bg/styles/buttons/twitter.png" /></a> ..." Line: 441 Column: 71 - 129
"... "_blank"><img src="http://www.omda.bg/styles/buttons/youtube.png" /></a> ..."

The “width” attribute on the “td” element is obsolete. Use CSS instead.

Line: 277 Column: 9 - 63
"...> <tr> <td width="300px" style = "border-right: 1px solid #aaa;"><div c..." Line: 314 Column: 39 - 63
".../div></td> <td width="300px" style = "border-right: 1px solid #aaa;"><div c..." Line: 351 Column: 39 - 23
".../div></td> <td width="300px" ><div c..."

Row 3 of a row group established by a “tbody” element has no cells beginning on it.

Line: 375 Column: 87 - 94
"...></td><tr></table></div>..."

Attribute “naturalsizeflag” not allowed on element “img” at this point.

Line: 438 Column: 53 - 299
"...="_blank"><img border="0" width="53" height="31" naturalsizeflag="0" title = "A BIG EYE Selection" alt="A BIG EYE Selection" src="http://www.omda.bg/styles/buttons/eye.jpg" style ="-webkit-border-radius: 5px; -moz-border-radius: 5px; border-radius: 5px;" /></a> ..."

Warnings

The “language” attribute on the “script” element is obsolete. You can safely omit it.

Line: 120 Column: 1 - 112
"...</script> <script language="javascript" type="text/javascript" src="http://www.omda.bg/common_files/java_scripts/main.js"></scri..." Line: 121 Column: 1 - 112
"...</script> <script language="javascript" type="text/javascript" src="http://www.omda.bg/common_files/java_scripts/menu.js"></scri..." Line: 122 Column: 1 - 124
"...</script> <script language="javascript" type="text/javascript" src="http://www.omda.bg/common_files/java_scripts/jquery-1.8.2.min.js"></scri..." Line: 123 Column: 1 - 127
"...</script> <script language="javascript" type="text/javascript" src="http://www.omda.bg/common_files/java_scripts/jquery.pajinate.min.js"></scri..." Line: 124 Column: 1 - 127
"...</script> <script language="javascript" type="text/javascript" src="http://www.omda.bg/common_files/java_scripts/jquery.colorbox-min.js"></scri..."

Empty heading.

Line: 375 Column: 63 - 66
"...bletItem"><h4></h4><..."

A table row was 0 columns wide, which is less than the column count established by the first row (4).

Line: 375 Column: 87 - 94
"...></td><tr></table></div>..."

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

omda.bg similar domains

Similar domains:

www.omda.com
www.omda.net
www.omda.org
www.omda.info
www.omda.biz
www.omda.us
www.omda.mobi
www.mda.bg
www.omda.bg
www.imda.bg
www.oimda.bg
www.iomda.bg
www.kmda.bg
www.okmda.bg
www.komda.bg
www.lmda.bg
www.olmda.bg
www.lomda.bg
www.pmda.bg
www.opmda.bg
www.pomda.bg
www.oda.bg
www.onda.bg
www.omnda.bg
www.onmda.bg
www.ojda.bg
www.omjda.bg
www.ojmda.bg
www.okda.bg
www.omkda.bg
www.oma.bg
www.omxa.bg
www.omdxa.bg
www.omxda.bg
www.omsa.bg
www.omdsa.bg
www.omsda.bg
www.omea.bg
www.omdea.bg
www.omeda.bg
www.omra.bg
www.omdra.bg
www.omrda.bg
www.omfa.bg
www.omdfa.bg
www.omfda.bg
www.omca.bg
www.omdca.bg
www.omcda.bg
www.omd.bg
www.omdq.bg
www.omdaq.bg
www.omdqa.bg
www.omdw.bg
www.omdaw.bg
www.omdwa.bg
www.omds.bg
www.omdas.bg
www.omdz.bg
www.omdaz.bg
www.omdza.bg

omda.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.

omda.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.

OMDA.BG Omda.bg

omda.bg Website Information

Advertisement

omda.bg Alexa Rank

omda.bg whois

omda.bg server information

Servers Location

omda.bg desktop page speed rank

omda.bg Desktop Speed Test Quick Summary

priority - 45Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 438.1KiB (90% reduction).

priority - 15Leverage 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 - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 6 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 1Reduce server response time

priority - 1Minify 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 6.2KiB (25% reduction).

priority - 0Minify 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 1.7KiB (23% reduction).

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 1.1KiB (15% reduction).

omda.bg Desktop Resource Breakdown

omda.bg mobile page speed rank

omda.bg Mobile Speed Test Quick Summary

priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 8 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Use asynchronous versions of the following scripts:

Optimize CSS Delivery of the following:

priority - 22Leverage 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 - 9Reduce server response time

priority - 1Minify 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 6.2KiB (25% reduction).

priority - 0Minify 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 1.7KiB (23% reduction).

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 1.1KiB (15% reduction).

priority - 0Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 530B (11% reduction).

omda.bg Mobile Resource Breakdown

omda.bg mobile page usability

omda.bg Mobile Usability Test Quick Summary

priority - 37Use 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.

priority - 25Size 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.

priority - 14Size 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 1,202 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

priority - 10Configure 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.

omda.bg HTML validation

Errors

Obsolete doctype. Expected “<!DOCTYPE html>”.

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Bad value “description” for attribute “http-equiv” on element “meta”.

Attribute “name” not allowed on element “meta” at this point.

Bad value “keywords” for attribute “http-equiv” on element “meta”.

Element “input” is missing required attribute “alt”.

The “center” element is obsolete. Use CSS instead.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

The “width” attribute on the “td” element is obsolete. Use CSS instead.

Row 3 of a row group established by a “tbody” element has no cells beginning on it.