10.6 sec in total
3.5 sec
6.5 sec
635 ms
Welcome to yafah.com homepage info - get ready to check Yafah best content for Israel right away, or after learning these important things about yafah.com
موقع يافة كوم يرحب بكم. موقع اخباري،اعلامي، ثقافي، يشرفنا أن تكونوا من زواره.
Visit yafah.comWe analyzed Yafah.com page load time and found that the first response time was 3.5 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
yafah.com performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value1.9 s
98/100
25%
Value2.1 s
99/100
10%
Value0 ms
100/100
30%
Value0.014
100/100
15%
Value1.9 s
100/100
10%
3491 ms
264 ms
281 ms
282 ms
283 ms
Our browser made a total of 185 requests to load all elements on the main page. We found that 64% of them (118 requests) were addressed to the original Yafah.com, 11% (20 requests) were made to Static.xx.fbcdn.net and 8% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Yafah.com.
Page size can be reduced by 935.2 kB (42%)
2.2 MB
1.3 MB
In fact, the total size of Yafah.com main page is 2.2 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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 106.1 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 106.1 kB or 76% of the original size.
Potential reduce by 90.4 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. Yafah images are well optimized though.
Potential reduce by 722.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 722.6 kB or 64% of the original size.
Potential reduce by 16.1 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. Yafah.com needs all CSS files to be minified and compressed as it can save up to 16.1 kB or 83% of the original size.
Number of requests can be reduced by 49 (36%)
138
89
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yafah. 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 4 to 1 for CSS and as a result speed up the page load time.
yafah.com
3491 ms
jq.js
264 ms
cook.js
281 ms
scroll.js
282 ms
uploadfile.js
283 ms
arastar.css
285 ms
arastar.js
285 ms
gpt.js
7 ms
addthis_widget.js
12 ms
jwplayer.js
531 ms
infolinks_main.js
60 ms
ga.js
26 ms
pop.js
93 ms
MT152caDw4JDdXM.jpeg
518 ms
xclose.png
133 ms
radibutt.png
137 ms
shares.png
136 ms
logo.jpg
133 ms
bgtitle_2.jpg
134 ms
bgtitle_3.jpg
262 ms
bgtitle_4.jpg
266 ms
bgtitle_5.jpg
264 ms
bgtitle_6.jpg
265 ms
bgtitle_7.jpg
265 ms
bgtitle_8.jpg
386 ms
bgtitle_9.jpg
391 ms
bgtitle_10.jpg
392 ms
r6.jpg
396 ms
r2.jpg
393 ms
r1.jpg
393 ms
r4.jpg
514 ms
r3.jpg
547 ms
r5.jpg
549 ms
r7.jpg
550 ms
r8.jpg
550 ms
cro.php
1046 ms
cro.php
976 ms
watch.png
685 ms
cro.php
689 ms
cro.php
686 ms
cro.php
687 ms
cro.php
892 ms
cro.php
894 ms
title1.jpg
895 ms
cro.php
893 ms
title2.jpg
963 ms
cro.php
1095 ms
cro.php
1084 ms
pubads_impl_82.js
21 ms
cro.php
1077 ms
__utm.gif
39 ms
ads
68 ms
container.html
33 ms
checkInventory.php
120 ms
title3.jpg
951 ms
cro.php
978 ms
cro.php
1055 ms
cro.php
1214 ms
cro.php
1222 ms
ads
36 ms
cro.php
991 ms
cro.php
973 ms
cro.php
980 ms
cro.php
1058 ms
cro.php
1095 ms
icoplay.png
1096 ms
logo.png
59 ms
ads
38 ms
likebox.php
246 ms
ads
37 ms
pollins.php
1013 ms
Untitled-2.jpg
1064 ms
title115.jpg
1087 ms
cro.php
1094 ms
facebooktitle.jpg
1098 ms
title13.jpg
1102 ms
user_sync.html
41 ms
usersyncup-an.html
44 ms
ice.js
128 ms
300lo.json
58 ms
showad.js
15 ms
cro.php
1013 ms
sh.8e5f85691f9aaa082472a194.html
29 ms
PugMaster
38 ms
cro.php
1037 ms
title11.jpg
1061 ms
cro.php
1069 ms
cro.php
1071 ms
ebiMDO3r-8l.css
144 ms
jGc-59L_9lo.css
161 ms
k5BhlqovqZn.css
181 ms
1kPfZUdGrka.js
217 ms
Yuj_Y8xNH2C.js
241 ms
Mpe38fuBVZ2.js
201 ms
n8qIhCw3vMx.js
199 ms
d20DxWMAn1e.js
200 ms
qcMicXoOToy.js
273 ms
57RpJa05x58.js
260 ms
7B-2ZS3Qt8r.js
262 ms
pf3FNnit_ev.js
262 ms
BmFj6FmaQGO.js
238 ms
hGrOQrzI1QD.js
310 ms
qf1RiuO5N-I.js
313 ms
pixel
29 ms
Pug
25 ms
usersync.aspx
24 ms
Pug
80 ms
Pug
82 ms
Pug
82 ms
Pug
84 ms
Pug
21 ms
cro.php
944 ms
title12.jpg
971 ms
title4.jpg
1027 ms
cro.php
1183 ms
Pug
24 ms
1966941_654181958028739_6582269831836189549_n.jpg
124 ms
560972_264228910357381_546580238_n.jpg
207 ms
12688123_482838998579339_4157703671988182210_n.jpg
309 ms
10250165_185697235145280_3601773695153838907_n.jpg
237 ms
5750_931279766966516_6963046786804317020_n.jpg
253 ms
1045053_1393081434051497_5732920331099470993_n.jpg
307 ms
11825142_1439301086400177_1705162503158324736_n.jpg
185 ms
1013609_103689993361124_559155368226165422_n.jpg
224 ms
10325292_191799824529451_8585226266495209275_n.jpg
244 ms
12803091_906564876118085_2180968479434354959_n.jpg
278 ms
12742453_996088127150237_9103390597380852222_n.jpg
321 ms
10338763_481424775392572_3122321187039451134_n.jpg
258 ms
12798844_1523126561316043_4658094699713467427_n.jpg
407 ms
11221721_1631635490418317_1816594988400946071_n.jpg
286 ms
12717819_596989577119759_3367835904194905320_n.jpg
356 ms
wL6VQj7Ab77.png
71 ms
s7jcwEQH7Sx.png
72 ms
cro.php
864 ms
cro.php
862 ms
cro.php
868 ms
title25.jpg
829 ms
gxbPuQdXIZP.png
27 ms
cro.php
876 ms
cro.php
918 ms
cro.php
839 ms
cro.php
814 ms
title889.jpg
836 ms
cro.php
889 ms
cro.php
912 ms
cro.php
918 ms
cro.php
845 ms
title6.jpg
804 ms
cro.php
828 ms
cro.php
883 ms
VXcANLwwL5J.js
24 ms
AmlxWlqMvlv.js
35 ms
cro.php
824 ms
cro.php
816 ms
title5.jpg
804 ms
cro.php
803 ms
cro.php
830 ms
cro.php
855 ms
cro.php
831 ms
title7.jpg
808 ms
cro.php
803 ms
cro.php
802 ms
cro.php
829 ms
cro.php
860 ms
title8.jpg
827 ms
cro.php
809 ms
cro.php
807 ms
cro.php
803 ms
jar.jpg
830 ms
cro.php
863 ms
cro.php
828 ms
cro.php
800 ms
cro.php
801 ms
tou.jpg
802 ms
cro.php
802 ms
cro.php
805 ms
cro.php
804 ms
cro.php
795 ms
cro.php
793 ms
cro.php
795 ms
xxx.png
802 ms
bg_y.png
805 ms
bg_search.png
797 ms
x.png
790 ms
vico.png
790 ms
yafah.com 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.
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
Links do not have a discernible name
yafah.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
yafah.com 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
AR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yafah.com can be misinterpreted by Google and other search engines. Our service has detected that Arabic 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 Yafah.com 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.
yafah.com
Open Graph description is not detected on the main page of Yafah. 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: