9.2 sec in total
552 ms
8.1 sec
496 ms
Visit urbano.in now to see the best up-to-date Urbano content and also check out these interesting facts you probably never knew about urbano.in
Urbano.in to provide you with the best quality plants and planters for Home, Kitchen Like Indoor Plants, Kitchen Garden Plants, Orchid Plant, etc. ✯Shop Now
Visit urbano.inWe analyzed Urbano.in page load time and found that the first response time was 552 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
urbano.in performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value7.4 s
4/100
25%
Value7.8 s
23/100
10%
Value1,130 ms
22/100
30%
Value0.049
99/100
15%
Value14.0 s
10/100
10%
552 ms
424 ms
31 ms
427 ms
424 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 73% of them (60 requests) were addressed to the original Urbano.in, 6% (5 requests) were made to Googleads.g.doubleclick.net and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Urbano.in.
Page size can be reduced by 161.7 kB (7%)
2.2 MB
2.0 MB
In fact, the total size of Urbano.in 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 147.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 147.1 kB or 82% of the original size.
Potential reduce by 12.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. Urbano images are well optimized though.
Potential reduce by 750 B
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 985 B
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. Urbano.in has all CSS files already compressed.
Number of requests can be reduced by 47 (60%)
78
31
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Urbano. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
urbano.in
552 ms
6lolv.css
424 ms
css
31 ms
6lolv.css
427 ms
6lomf.css
424 ms
6lolv.css
534 ms
6lolv.css
431 ms
post-6292.css
441 ms
post-550.css
734 ms
6lolv.css
739 ms
post-285.css
439 ms
css
16 ms
6lomf.css
839 ms
6lolv.js
445 ms
6lolv.js
939 ms
js
61 ms
js
133 ms
adsbygoogle.js
117 ms
js
133 ms
6lomf.js
1073 ms
email-decode.min.js
532 ms
6lolv.css
1071 ms
style.min.js
1245 ms
woocommerce-oneclick-upsell-funnel-public.js
1245 ms
jquery.blockUI.min.js
1319 ms
add-to-cart.min.js
1437 ms
js.cookie.min.js
1437 ms
woocommerce.min.js
1435 ms
cart-fragments.min.js
1646 ms
webpack.runtime.min.js
2663 ms
frontend-modules.min.js
2659 ms
waypoints.min.js
3700 ms
core.min.js
3692 ms
frontend.min.js
3689 ms
underscore.min.js
3703 ms
wp-util.min.js
4957 ms
frontend.min.js
4956 ms
fbevents.js
217 ms
show_ads_impl.js
397 ms
zrt_lookup.html
272 ms
URBANO-LOGO-BLACK.png
3894 ms
WhatsApp-Image-2020-07-17-at-1.03.49-PM-1.jpeg
4212 ms
urbano-website-banner-3.jpg
4262 ms
WhatsApp-Image-2020-07-17-at-1.03.49-PM.jpeg
3892 ms
kauna-grass-profile.jpg
4803 ms
cane-planter-profile.jpg
4520 ms
bamboo-planter-profile.jpg
4619 ms
houseplants-pack.jpg
5005 ms
plant2-free-img.png
4727 ms
IMG_20211203_173923-300x300.jpg
4678 ms
Bamboo-Lampshade-Neon-300x300.jpg
4927 ms
WhatsApp-Image-2020-07-21-at-2.13.39-PM-1-300x300.jpeg
5030 ms
FB_IMG_1623336121882-1-300x300.jpg
5192 ms
IMG_20210922_215818-300x300.jpg
5231 ms
20220110_124046-300x300.jpg
5301 ms
round-grass-planter-300x300.jpg
5331 ms
PicsArt_01-30-02.36.32-1-300x300.jpg
5412 ms
plant1-free-img.png
5444 ms
arjun.jpg
5803 ms
quote-free-img.png
5692 ms
js
199 ms
analytics.js
315 ms
265 ms
user2-free-img.jpg
5737 ms
206 ms
329 ms
sourav.jpg
5606 ms
about-bg-free-img.jpg
5801 ms
LhWlMVbYOfASNfNUZF4_Yw.woff
252 ms
fa-brands-400.woff
5842 ms
astra.woff
5766 ms
compost-e1591386932659.png
5818 ms
water-spray-e1591386979918.jpg
5874 ms
136 ms
collect
43 ms
77 ms
ads
86 ms
collect
49 ms
35 ms
ga-audiences
25 ms
urbano.in
2510 ms
6lolv.css
10 ms
urbano.in 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
Links do not have a discernible name
urbano.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
urbano.in 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Urbano.in 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 Urbano.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.
urbano.in
Open Graph data is detected on the main page of Urbano. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: