2.9 sec in total
479 ms
2.2 sec
248 ms
Visit yes.no now to see the best up-to-date Yes content for Israel and also check out these interesting facts you probably never knew about yes.no
yes.no is a Q&A social network that lets you ask the people you admire the things you've always wanted to know.
Visit yes.noWe analyzed Yes.no page load time and found that the first response time was 479 ms and then it took 2.4 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.no performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.7 s
16/100
25%
Value6.2 s
42/100
10%
Value110 ms
98/100
30%
Value0.001
100/100
15%
Value7.6 s
46/100
10%
479 ms
57 ms
839 ms
120 ms
70 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 29% of them (28 requests) were addressed to the original Yes.no, 44% (43 requests) were made to Res.cloudinary.com and 5% (5 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Yes.no.
Page size can be reduced by 188.0 kB (24%)
792.3 kB
604.3 kB
In fact, the total size of Yes.no main page is 792.3 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. Images take 491.2 kB which makes up the majority of the site volume.
Potential reduce by 45.3 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 15.2 kB, which is 27% 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 45.3 kB or 80% of the original size.
Potential reduce by 3.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. Yes images are well optimized though.
Potential reduce by 120.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 120.9 kB or 55% of the original size.
Potential reduce by 18.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. Yes.no needs all CSS files to be minified and compressed as it can save up to 18.3 kB or 77% of the original size.
Number of requests can be reduced by 37 (39%)
96
59
The browser has sent 96 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 31 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
yes.no
479 ms
bootstrap_3.3.4.min.css
57 ms
main.scss.css
839 ms
bootstrap_social.css
120 ms
client:platform.js
70 ms
core.css
157 ms
bootstrap.css
463 ms
textcomplete.css
574 ms
nprogress.css
104 ms
font-awesome.min.css
34 ms
jquery-2.1.3.min.js
167 ms
lib.js
450 ms
textcomplete.min.js
822 ms
main.js
213 ms
fb_sdk.js
1024 ms
jquery.autocomplete.min.js
495 ms
bootstrap_3.3.4.min.js
898 ms
fastClick.js
539 ms
alertify.js
965 ms
jquery.ui.widget.js
964 ms
jquery.iframe-transport.js
964 ms
jquery.fileupload.js
963 ms
jquery.cloudinary.js
1020 ms
autogrow.js
1019 ms
nprogress.js
1042 ms
branch-v2.0.0.min.js
36 ms
_r
113 ms
open
482 ms
gtm.js
135 ms
hfsh0jd7hn9aj1on3j9o.jpg
263 ms
ciq15nn42s7ippwni9n1.jpg
262 ms
gqvsim9hfzv5jtgbexzz.jpg
245 ms
kscohqfxd1yrendod9gp.jpg
259 ms
zxfigqvcgt9bbc8wg4zh.jpg
258 ms
vrd8seunlwkvjkyedyir.jpg
243 ms
fxmakimyckpxw2hjwfp3.jpg
288 ms
gv0q8tbugopymxnnlrte.jpg
288 ms
kctmaquxelgwknjqbmcd.jpg
299 ms
rcvd2jvlcq0hwqxkavck.jpg
299 ms
tkhcgbdqiiftceard9bc.jpg
299 ms
ysexwz40tx2eoul9z6zg.jpg
297 ms
bdxpybwsdy27bl8ntlui.png
362 ms
hafs1jl1wzu3wb7bdmib.jpg
345 ms
ubl52vlvjajmlle9fmj2.jpg
360 ms
aiwcs6cqotxf38sscrdk.jpg
360 ms
xz2rw09vhiivd0fiqcgw.jpg
359 ms
ue9vej2clsup3bjwuirl.png
362 ms
pegl054n9t2if7usfw4x.jpg
360 ms
ovkhv5a01c6acpricy5c.jpg
403 ms
xrdon16pg0ya7eja3ey1.png
434 ms
q0zfzvvk71lqkgecjn28.jpg
439 ms
j9rer0kv1d6gnzqgdtvv.jpg
399 ms
fatsajlotg55ybswcb6e.jpg
399 ms
uqtq7nii1oiyjbypi3af.jpg
399 ms
fcdahrknw25rfcp9yicy.jpg
439 ms
tq7tbrmkvhgn5wyb0kng.jpg
438 ms
lokqhgr7infxepu3ymm6.jpg
438 ms
oz9uintkjo5ympam8jmq.jpg
438 ms
sssg5edxdynrklhxnxuh.jpg
438 ms
frf9l9e6owuxso82adjc.jpg
467 ms
vgagngsowmaoa4fsgxnw.jpg
463 ms
j2wg5p05n2rdifqitlpq.jpg
464 ms
qcmjr8jrt5imenp1zadq.jpg
489 ms
rxyybfgn3hxf3tfkn3p7.png
489 ms
jkcobci2tmofu8bwoytr.jpg
481 ms
lp_bg_4.jpg
176 ms
yesno-logo.png
174 ms
exp1.jpg
248 ms
exp2.jpg
277 ms
exp3.jpg
247 ms
cb=gapi.loaded_0
27 ms
postmessageRelay
110 ms
sdk.js
143 ms
fontawesome-webfont.woff
36 ms
w.js
110 ms
mixpanel-2-latest.min.js
208 ms
analytics.js
106 ms
cb=gapi.loaded_1
43 ms
l41s7ehwn8usgjmr2w0r.jpg
258 ms
tsrsjbqlqcvshmf1mjxv.jpg
250 ms
n4dwaxdwdmlsynqvmbvm.jpg
243 ms
n6visqrt7xk9eq3b42vl.jpg
261 ms
ehnidg6nwkbjokmhatje.jpg
288 ms
znhkbiqnmbenxmi46qoy.jpg
268 ms
3193398744-postmessagerelay.js
75 ms
rpc:shindig_random.js
74 ms
iframe
29 ms
dykstpfykbla5rajwtrv.jpg
247 ms
clickstream.min.js
76 ms
1233565733-idpiframe.js
47 ms
collect
48 ms
cb=gapi.loaded_0
19 ms
149 ms
xd_arbiter.php
51 ms
iframerpc
72 ms
storage.luckyorange.net
80 ms
36 ms
settings.luckyorange.net
115 ms
yes.no accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
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.
yes.no 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
yes.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yes.no can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Yes.no 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.no
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: