12.1 sec in total
538 ms
11.4 sec
223 ms
Click here to check amazing Yebber content for India. Otherwise, check out these important facts you probably never knew about yebber.com
Yebber: Real reviews from real people of restaurants, food, shops, hotels, and more in Singapore!
Visit yebber.comWe analyzed Yebber.com page load time and found that the first response time was 538 ms and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yebber.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value11.8 s
0/100
25%
Value20.5 s
0/100
10%
Value1,190 ms
21/100
30%
Value0.654
8/100
15%
Value15.7 s
6/100
10%
538 ms
1017 ms
1124 ms
583 ms
640 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 77% of them (90 requests) were addressed to the original Yebber.com, 6% (7 requests) were made to Pagead2.googlesyndication.com and 3% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Yebber.com.
Page size can be reduced by 129.3 kB (14%)
921.4 kB
792.1 kB
In fact, the total size of Yebber.com main page is 921.4 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. 55% of websites need less resources to load. Javascripts take 586.8 kB which makes up the majority of the site volume.
Potential reduce by 96.0 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 96.0 kB or 83% of the original size.
Potential reduce by 24.7 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, Yebber needs image optimization as it can save up to 24.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 4.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. Yebber.com needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 25% of the original size.
Number of requests can be reduced by 33 (29%)
115
82
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yebber. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
yebber.com
538 ms
www.yebber.com
1017 ms
style-v30.css
1124 ms
lightbox.css
583 ms
jquery.fancybox.css
640 ms
jquery.fancybox-buttons.css
45 ms
jquery.min.js
22 ms
slides.min.jquery.js
41 ms
adsbygoogle.js
97 ms
counter_xhtml.js
60 ms
lightbox.v1.compressed.js
638 ms
bsn.AutoSuggest_2.1.3_comp.js
1481 ms
jquery.fancybox.pack.js
913 ms
jquery.fancybox-buttons.js
1110 ms
jquery.fancybox-media.js
654 ms
jquery.fancybox-thumbs.js
1171 ms
consolidated-java-1.1.js
1249 ms
logo-sg.gif
743 ms
whatisyebber.gif
1297 ms
1.jpg
1012 ms
2.jpg
1260 ms
3.gif
938 ms
4.gif
1084 ms
5.gif
1765 ms
7.gif
2527 ms
7997_s.gif
1564 ms
playmade1-50x50.png
1840 ms
playmade2-50x50.png
2046 ms
playmade3-50x50.png
2122 ms
playmadenex-50x50.jpg
2132 ms
playmade-menu-50x50.jpg
2291 ms
saveur-purvis-street-1-50x50.jpg
2363 ms
saveur-purvis-street-2-50x50.jpg
2570 ms
saveur-purvis-street-3-50x50.jpg
2667 ms
saveur-purvis-street-4-50x50.jpg
2681 ms
saveur-purvis-street-5-50x50.jpg
2859 ms
16_s.jpg
2913 ms
g03-50x50.jpg
3073 ms
g02-50x50.jpg
3087 ms
g05-50x50.jpg
3212 ms
g07-50x50.jpg
3222 ms
g01-50x50.jpg
3409 ms
1-50x50.jpg
3452 ms
2-50x50.jpg
3605 ms
3-50x50.jpg
3616 ms
4-50x50.jpg
3744 ms
5-50x50.jpg
3499 ms
g03-50x50.jpg
4885 ms
g4-50x50.jpg
4009 ms
analytics.js
28 ms
g02-50x50.jpg
4051 ms
sdk.js
79 ms
afr.php
4645 ms
collect
94 ms
show_ads_impl.js
282 ms
sdk.js
20 ms
g01-50x50.jpg
4395 ms
t.php
203 ms
44 ms
js
75 ms
b03-50x50.jpg
3711 ms
zrt_lookup.html
33 ms
ads
462 ms
ads
251 ms
b04-50x50.jpg
3818 ms
b02-50x50.jpg
3679 ms
b01-50x50.jpg
3587 ms
img_6062-50x50.jpg
3950 ms
003-50x50.jpg
3849 ms
img_6063-50x50.jpg
3855 ms
jidechishopfront-50x50.jpg
3587 ms
img_6061-50x50.jpg
3463 ms
event-1-50x50.jpg
3588 ms
img_5828-50x50.jpg
3526 ms
img_5829-50x50.jpg
3520 ms
img_5830-50x50.jpg
3536 ms
event-2-50x50.jpg
3370 ms
img_5836-50x50.jpg
3407 ms
82-3-50x50.jpg
3423 ms
img_5837-50x50.jpg
3531 ms
plus82-50x50.jpg
3491 ms
img_5835-50x50.jpg
3512 ms
nophoto_s.jpg
3344 ms
img_0996-50x50.png
3394 ms
706_s.jpg
3415 ms
l1010656_zps0xhcvnbg-50x50.jpg
3551 ms
l1010657_zpsefqnq017-50x50.jpg
3477 ms
l1010661_zpsmvckwipr-50x50.jpg
3483 ms
l1010664_zpsqndo3klr-50x50.jpg
3327 ms
l1010673_zpsgqpeolco-50x50.jpg
3400 ms
bullet_arrow_down.gif
3518 ms
resizeImage.php
3664 ms
creditcardpromo.gif
3363 ms
playmade-menu-150x150.jpg
3982 ms
playmadenex-150x150.jpg
3740 ms
yd.png
3589 ms
yebber-search-bar2.gif
4167 ms
shadow.gif
3017 ms
stars_sm.png
3509 ms
blackbar.png
3205 ms
loading.gif
4055 ms
adj.php
485 ms
close.png
3527 ms
lg.php
3413 ms
show_ads.js
64 ms
viewability.js
21 ms
advr.php
230 ms
adsbygoogle.js
88 ms
show_ads_impl.js
226 ms
ads
475 ms
advc.php
969 ms
fancybox_sprite.png
971 ms
sodar
79 ms
sodar2.js
15 ms
runner.html
6 ms
aframe
49 ms
q3_ozqIbHCwHEmDedgzG-D6UnUyzi2L496FFdqoLokA.js
3 ms
yebber.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.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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>).
yebber.com 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
Page has valid source maps
yebber.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Yebber.com 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 Yebber.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.
yebber.com
Open Graph description is not detected on the main page of Yebber. 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: