10.5 sec in total
2 sec
7.9 sec
568 ms
Welcome to yellr.in homepage info - get ready to check Yellr best content right away, or after learning these important things about yellr.in
Visit yellr.inWe analyzed Yellr.in page load time and found that the first response time was 2 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yellr.in performance score
2006 ms
922 ms
26 ms
445 ms
451 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 90% of them (78 requests) were addressed to the original Yellr.in, 3% (3 requests) were made to Fonts.googleapis.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Yellr.in.
Page size can be reduced by 168.5 kB (45%)
378.1 kB
209.5 kB
In fact, the total size of Yellr.in main page is 378.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. 60% of websites need less resources to load. CSS take 209.5 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.6 kB or 79% of the original size.
Potential reduce by 0 B
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. Yellr images are well optimized though.
Potential reduce by 127.9 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. Yellr.in needs all CSS files to be minified and compressed as it can save up to 127.9 kB or 61% of the original size.
Number of requests can be reduced by 45 (57%)
79
34
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yellr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
yellr.in
2006 ms
layerslider.css
922 ms
css
26 ms
styles.css
445 ms
tp_twitter_plugin.css
451 ms
settings.css
1337 ms
style.css
470 ms
base.css
676 ms
buttons.css
677 ms
mfn-icons.css
1333 ms
grid.css
924 ms
layout.css
1335 ms
shortcodes.css
1972 ms
variables.css
1140 ms
animations.min.css
2064 ms
colorpicker.css
1363 ms
jquery.ui.all.css
1784 ms
jplayer.blue.monday.css
1564 ms
prettyPhoto.css
1559 ms
responsive-1240.css
1802 ms
responsive.css
1781 ms
style.css
1807 ms
style.php
2533 ms
css
25 ms
css
26 ms
custom.css
1997 ms
jquery.js
2704 ms
jquery-migrate.min.js
2058 ms
layerslider.kreaturamedia.jquery.js
2422 ms
greensock.js
2652 ms
layerslider.transitions.js
2286 ms
jquery.themepunch.tools.min.js
2946 ms
jquery.themepunch.revolution.min.js
3164 ms
jquery.form.min.js
2240 ms
scripts.js
2355 ms
core.min.js
2475 ms
widget.min.js
2479 ms
mouse.min.js
2512 ms
sortable.min.js
2817 ms
tabs.min.js
2691 ms
accordion.min.js
2683 ms
animations.min.js
2705 ms
jquery.jplayer.min.js
2951 ms
colorpicker.js
2663 ms
jquery.plugins.js
3766 ms
mfn.menu.js
2454 ms
scripts.js
2690 ms
comment-reply.min.js
2303 ms
box_shadow.png
377 ms
logo.png
436 ms
home_spa_slider1.jpg
1794 ms
slide-hotel-1-bg.jpg
2007 ms
slide-hotel-2-bg.jpg
1470 ms
spa.jpg
1522 ms
hotel_box_1.jpg
685 ms
hotel_box_2.jpg
924 ms
hotel_box_3.jpg
1150 ms
hotel_about.jpg
1586 ms
hotel_bell.png
1482 ms
hotel_price.png
1689 ms
home_spa_slider_41.jpg
1953 ms
home_spa_slider_31.jpg
1964 ms
home_spa_slider_21.jpg
2043 ms
home_spa_slider_11.jpg
2145 ms
bankHomepage_Banner_31-80x80.jpg
2042 ms
slide-hotel-1-bg-80x80.jpg
2188 ms
g40.png
2170 ms
box_shadow_button.png
2182 ms
list_star.png
2256 ms
textline.png
2236 ms
blockquote.png
2319 ms
section_price.jpg
2374 ms
section_plans.jpg
3049 ms
stripes_3_b.png
2398 ms
recent_comments.png
2461 ms
list_check.png
2470 ms
list_idea.png
2534 ms
mfn-icons.woff
2817 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
58 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
59 ms
yAXhog6uK3bd3OwBILv_SKCWcynf_cDxXwCLxiixG1c.ttf
7 ms
slide-hotel-1-thumb.jpg
705 ms
loader.gif
1299 ms
tp-leftarrow.png
1355 ms
tp-rightarrow.png
1360 ms
slide-hotel-2-thumb.jpg
460 ms
slide-hotel-1-thumb.jpg
328 ms
yellr.in SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yellr.in 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 Yellr.in 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.
yellr.in
Open Graph description is not detected on the main page of Yellr. 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: