4.4 sec in total
950 ms
3.3 sec
140 ms
Click here to check amazing Habesha content. Otherwise, check out these important facts you probably never knew about habesha.biz
HabeshaBiz Ethiopian business directory. Habesha.Biz is your reliable online promoter
Visit habesha.bizWe analyzed Habesha.biz page load time and found that the first response time was 950 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
habesha.biz performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value4.5 s
37/100
25%
Value20.2 s
0/100
10%
Value3,080 ms
2/100
30%
Value0.025
100/100
15%
Value7.8 s
44/100
10%
950 ms
500 ms
333 ms
276 ms
184 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 57% of them (37 requests) were addressed to the original Habesha.biz, 15% (10 requests) were made to Static.xx.fbcdn.net and 14% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (950 ms) belongs to the original domain Habesha.biz.
Page size can be reduced by 471.0 kB (74%)
634.6 kB
163.6 kB
In fact, the total size of Habesha.biz main page is 634.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. 35% of websites need less resources to load. CSS take 272.9 kB which makes up the majority of the site volume.
Potential reduce by 24.5 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 24.5 kB or 79% of the original size.
Potential reduce by 9.9 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. Obviously, Habesha needs image optimization as it can save up to 9.9 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 186.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 186.5 kB or 71% of the original size.
Potential reduce by 250.0 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. Habesha.biz needs all CSS files to be minified and compressed as it can save up to 250.0 kB or 92% of the original size.
Number of requests can be reduced by 39 (63%)
62
23
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Habesha. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
habesha.biz
950 ms
bootstrap.css
500 ms
main.css
333 ms
font-awesome.css
276 ms
demo.css
184 ms
css
24 ms
style.css
272 ms
jquery.min.js
446 ms
slider.css
364 ms
modernizr.custom.28468.js
366 ms
jquery.cslider.js
368 ms
move-top.js
419 ms
easing.js
454 ms
normalize.css
458 ms
icons.css
461 ms
component.css
532 ms
modernizr.custom.js
537 ms
owl.carousel.css
544 ms
owl.theme.css
551 ms
zerogrid.css
554 ms
style.css
578 ms
responsive.css
586 ms
responsiveslides.css
628 ms
script.js
647 ms
meny.js
727 ms
jquery.flexisel.js
573 ms
owl.carousel.js
590 ms
analytics.js
21 ms
logo.png
121 ms
search.png
121 ms
TelalakiLogo.jpg
87 ms
icon-facebook.png
120 ms
icon-google(1).png
121 ms
icon-youtube-text.png
190 ms
icon-twitter.png
191 ms
collect
12 ms
collect
83 ms
sdk.js
172 ms
favicon.png
105 ms
mail.png
104 ms
top-move.jpg
97 ms
fontawesome-webfont.woff
211 ms
154 ms
xd_arbiter.php
165 ms
xd_arbiter.php
294 ms
like_box.php
168 ms
hDvwL1_H7g-.css
182 ms
56WNbrUYLbL.css
224 ms
q68gy-v_YMF.js
305 ms
FJmpeSpHpjS.js
377 ms
0wM5s1Khldu.js
302 ms
1bNoFZUdlYZ.js
299 ms
11113773_554809757992674_3798628947354067069_n.png
279 ms
10477524_554809324659384_4906857534489603810_n.png
318 ms
12717473_895721407213246_3054347537792492787_n.jpg
516 ms
12801514_164623857260276_5211839184803868670_n.jpg
396 ms
12509027_931906626929329_2068008625606519817_n.jpg
397 ms
1379841_10150004552801901_469209496895221757_n.jpg
396 ms
262290_129427050784545_448146377604379067_n.jpg
452 ms
10391470_103621903369901_142543567408234546_n.jpg
446 ms
10354686_10150004552801856_220367501106153455_n.jpg
433 ms
wL6VQj7Ab77.png
48 ms
s7jcwEQH7Sx.png
49 ms
I6-MnjEovm5.js
43 ms
pQrUxxo5oQp.js
83 ms
habesha.biz 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
habesha.biz 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
habesha.biz SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Habesha.biz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Habesha.biz 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.
habesha.biz
Open Graph description is not detected on the main page of Habesha. 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: