4.2 sec in total
629 ms
3.2 sec
365 ms
Visit yellow.ug now to see the best up-to-date Yellow content for Uganda and also check out these interesting facts you probably never knew about yellow.ug
Business Directory Uganda, List of Companies in Uganda with Contact Details, Addresses. Uganda Companies, Uganda Directory Listing.
Visit yellow.ugWe analyzed Yellow.ug page load time and found that the first response time was 629 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
yellow.ug performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value11.1 s
0/100
25%
Value6.5 s
39/100
10%
Value1,830 ms
9/100
30%
Value0.001
100/100
15%
Value13.5 s
11/100
10%
629 ms
116 ms
228 ms
36 ms
60 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 20% of them (14 requests) were addressed to the original Yellow.ug, 21% (15 requests) were made to Scontent.xx.fbcdn.net and 14% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (629 ms) belongs to the original domain Yellow.ug.
Page size can be reduced by 1.1 MB (66%)
1.6 MB
549.7 kB
In fact, the total size of Yellow.ug main page is 1.6 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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 213.6 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 213.6 kB or 89% of the original size.
Potential reduce by 19.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. Yellow images are well optimized though.
Potential reduce by 801.9 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 801.9 kB or 75% of the original size.
Potential reduce by 47.3 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. Yellow.ug needs all CSS files to be minified and compressed as it can save up to 47.3 kB or 79% of the original size.
Number of requests can be reduced by 23 (36%)
64
41
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yellow. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.yellow.ug
629 ms
main.min.css
116 ms
index.css
228 ms
css
36 ms
jquery.min.js
60 ms
adsbygoogle.js
6 ms
jquery.autocomplete.min.js
250 ms
analytics.js
40 ms
ug.jpg
561 ms
logo_ug.png
142 ms
stripe_main.png
229 ms
ca-pub-3351151485848212.js
77 ms
zrt_lookup.html
122 ms
show_ads_impl.js
71 ms
collect
54 ms
collect
52 ms
fancybox_overlay.png
198 ms
stripe_icategories.png
237 ms
screens.jpg
350 ms
stripe_ih2.png
237 ms
star.png
291 ms
star_on.png
291 ms
shareaholic.js
50 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
48 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
58 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
57 ms
loading2.gif
465 ms
pla
46 ms
all.js
204 ms
plusone.js
95 ms
shrMain.min.js
12 ms
8bc2c8980a786d47476605bb756ae2d4.json
123 ms
cb=gapi.loaded_0
61 ms
jquery.min.js
58 ms
pageview.gif
42 ms
139 ms
app.js
4 ms
xd_arbiter.php
155 ms
xd_arbiter.php
307 ms
angular.min.js
22 ms
shareaholic-icons.woff
4 ms
ping
50 ms
graph.facebook.com
35 ms
share
40 ms
page.php
108 ms
EdaViBk3jnl.css
173 ms
_rx8naC75Dy.js
248 ms
t-KLv3gqZy0.js
288 ms
uLtKx7ldlvR.js
361 ms
10628221_755999967801631_3495303643914322977_n.jpg
291 ms
10301063_756000184468276_2753522799927924767_n.png
327 ms
12219584_158246001196526_3374568908661638842_n.jpg
366 ms
10626459_720891371380230_5791274462871893614_n.jpg
402 ms
12806095_982426165169825_6582897696597886604_n.jpg
403 ms
11949338_10207925113185627_7273121927253987704_n.jpg
404 ms
12027624_696613223773838_1055440578126825380_n.jpg
411 ms
1496724_1746428452253549_492221155303911603_n.jpg
410 ms
12234866_863984947048018_2091050524849953967_n.jpg
416 ms
12642982_1681912018735013_8821436957778540259_n.jpg
486 ms
11248254_994051690639527_8221557389572740023_n.jpg
439 ms
12299197_149650388726204_7995633496228839908_n.jpg
440 ms
12715270_1565111910446066_4555535429316465477_n.jpg
450 ms
12524005_10204009818965375_131042021228108423_n.jpg
451 ms
12705292_119970778389074_1326023930910309317_n.jpg
455 ms
wL6VQj7Ab77.png
42 ms
CSXXCvknpgK.png
42 ms
R9a_DtVRZgv.js
40 ms
cUDgRFxaoIk.js
41 ms
0JBr1QHp8Gi.js
43 ms
kDOzhTr2W91.js
75 ms
yellow.ug accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
yellow.ug 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
yellow.ug SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yellow.ug can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Yellow.ug 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.
yellow.ug
Open Graph description is not detected on the main page of Yellow. 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: