2.8 sec in total
173 ms
2.4 sec
246 ms
Welcome to yes.af homepage info - get ready to check Yes best content for Afghanistan right away, or after learning these important things about yes.af
Get the latest job announcements in Afghanistan by UN, Government, International development agencies, Aid Agencies, Private Companies, MNCs
Visit yes.afWe analyzed Yes.af page load time and found that the first response time was 173 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
yes.af performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value3.3 s
70/100
25%
Value0
0/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.5 s
98/100
10%
173 ms
252 ms
333 ms
90 ms
118 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 24% of them (21 requests) were addressed to the original Yes.af, 31% (27 requests) were made to Static.xx.fbcdn.net and 9% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (598 ms) relates to the external source Facebook.com.
Page size can be reduced by 561.6 kB (63%)
885.1 kB
323.5 kB
In fact, the total size of Yes.af main page is 885.1 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. 65% of websites need less resources to load. Javascripts take 543.5 kB which makes up the majority of the site volume.
Potential reduce by 56.7 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. This page needs HTML code to be minified as it can gain 12.9 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 56.7 kB or 83% of the original size.
Potential reduce by 6.8 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. Yes images are well optimized though.
Potential reduce by 338.6 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 338.6 kB or 62% of the original size.
Potential reduce by 159.5 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. Yes.af needs all CSS files to be minified and compressed as it can save up to 159.5 kB or 81% of the original size.
Number of requests can be reduced by 52 (68%)
76
24
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
yes.af
173 ms
www.yes.af
252 ms
www.yes.af
333 ms
jquery.min.js
90 ms
styles.css
118 ms
pager.css
124 ms
jquery.ba-bbq.js
149 ms
bootstrap.min.css
167 ms
app.css
139 ms
custom.css
142 ms
platform.js
46 ms
adsbygoogle.js
21 ms
jquery-ui.min.css
146 ms
jquery-ui.min.js
254 ms
bootstrap.min.js
243 ms
font-awesome.min.css
242 ms
jquery.scrollTo.min.js
238 ms
custom.js
238 ms
jquery.yiigridview.js
238 ms
sdk.js
219 ms
likebox.php
598 ms
yes-top.png
70 ms
logo.png
86 ms
ca-pub-8186203663529678.js
55 ms
zrt_lookup.html
99 ms
show_ads_impl.js
99 ms
analytics.js
106 ms
ui-bg_flat_75_ffffff_40x100.png
135 ms
fontawesome-webfont.woff
162 ms
ads
255 ms
osd.js
15 ms
ads
382 ms
collect
19 ms
10 ms
xd_arbiter.php
126 ms
css
56 ms
m_js_controller.js
20 ms
abg.js
21 ms
favicon
103 ms
nessie_icon_thin_arrow_big_white.png
78 ms
s
77 ms
googlelogo_color_112x36dp.png
84 ms
x_button_blue2.png
62 ms
favicon
92 ms
favicon
40 ms
favicon
45 ms
favicon
69 ms
kyEKgjk51ZE.css
175 ms
xgj7bXhJNEH.css
184 ms
Czh0gDTFcBt.css
203 ms
kE_Z8j4XNUS.css
217 ms
N-k91nHCZS2.css
245 ms
ZeuPykSxSED.css
233 ms
q68gy-v_YMF.js
259 ms
FJmpeSpHpjS.js
257 ms
0wM5s1Khldu.js
221 ms
1bNoFZUdlYZ.js
243 ms
njO1TPvGzoR.js
257 ms
OloiM1PZafe.js
299 ms
LTv6ZK-5zxz.js
313 ms
1FCa-btixu2.js
305 ms
Oagsvfb4VWi.js
311 ms
pObvZSrFc_4.js
309 ms
Kt4tkgSRvHH.js
304 ms
H3EKDTObx05.js
309 ms
eR-qA8bp1RM.js
310 ms
1QuX41zDRrx.js
310 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
25 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
112 ms
12507666_940749122677241_5903459505706528606_n.jpg
272 ms
safe_image.php
267 ms
11666246_907589219326565_1468797498245589288_n.png
256 ms
12038396_1502752536702639_1580134456716018831_n.jpg
259 ms
12744268_106233873101345_508821003364425847_n.jpg
334 ms
12122634_551901134963767_2736392783913074417_n.jpg
295 ms
12540598_1733082466922069_3149380363797403839_n.jpg
280 ms
10659248_882950838446504_2750493481614261710_n.jpg
300 ms
12549098_175135462848364_8524500123034747229_n.jpg
281 ms
wL6VQj7Ab77.png
197 ms
s7jcwEQH7Sx.png
196 ms
QDwYpIaRyfG.png
197 ms
K00K-UgnsKu.png
197 ms
gxbPuQdXIZP.png
56 ms
I6-MnjEovm5.js
47 ms
pQrUxxo5oQp.js
48 ms
ui
39 ms
yes.af 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.
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
Links do not have a discernible name
yes.af best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
yes.af SEO score
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
FA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yes.af can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it does not match the claimed English language. Our system also found out that Yes.af 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.
yes.af
Open Graph data is detected on the main page of Yes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: