Tools & Wizards About Us
homelane.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

homelane.com

Best Interior Design Solutions in India | HomeLane

Page Load Speed

3.7 sec in total

First Response

28 ms

Resources Loaded

3 sec

Page Rendered

672 ms

homelane.com screenshot

About Website

Click here to check amazing Home Lane content for India. Otherwise, check out these important facts you probably never knew about homelane.com

Explore 1000's of fully customizable home interior designs. Get the interiors of your home designed by our experts at HomeLane. Book a free consultation today.

Visit homelane.com

Key Findings

We analyzed Homelane.com page load time and found that the first response time was 28 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

homelane.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value2,150 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.184

66/100

15%

TTI (Time to Interactive)

Value21.9 s

1/100

10%

Network Requests Diagram

homelane.com

28 ms

homelane.com

890 ms

www.homelane.com

1442 ms

bf57558972a97791f606.css

93 ms

141e8e7bc892246085f1.css

101 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Homelane.com, 84% (70 requests) were made to Ux-designs.homelane.com and 5% (4 requests) were made to Super.homelane.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Homelane.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 272.5 kB (76%)

Content Size

360.2 kB

After Optimization

87.7 kB

  • HTML
  • Images

In fact, the total size of Homelane.com main page is 360.2 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. 70% of websites need less resources to load. HTML takes 341.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 272.5 kB

  • Original 341.5 kB
  • After minification 341.3 kB
  • After compression 68.9 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 272.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 18.7 kB
  • After minification 18.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. Home Lane images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 70 (92%)

Requests Now

76

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Home Lane. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

homelane.com

homelane.com

28 ms

homelane.com

homelane.com

890 ms

www.homelane.com

www.homelane.com

1442 ms

bf57558972a97791f606.css

bf57558972a97791f606.css

93 ms

141e8e7bc892246085f1.css

141e8e7bc892246085f1.css

101 ms

c44b1e2cc18ac94bc308.css

c44b1e2cc18ac94bc308.css

93 ms

aa3250ed511a31c4e93c.css

aa3250ed511a31c4e93c.css

98 ms

9b2cf8decfe1cb4a6cf6.css

9b2cf8decfe1cb4a6cf6.css

95 ms

404e7fd4e4a4979fb4b6.css

404e7fd4e4a4979fb4b6.css

96 ms

b4ada5cab2e5d3522e98.css

b4ada5cab2e5d3522e98.css

106 ms

d1dfd80549978a54c0e5.css

d1dfd80549978a54c0e5.css

109 ms

0489b3970f8559ef1223.css

0489b3970f8559ef1223.css

107 ms

26f46f66dd98e9a9078c.css

26f46f66dd98e9a9078c.css

108 ms

8fc250b427a578a7d2f5.css

8fc250b427a578a7d2f5.css

107 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

118 ms

7840.ed77f44d70bebe4a98a4.js

7840.ed77f44d70bebe4a98a4.js

120 ms

97767-5b7f879965ae0035e894.js

97767-5b7f879965ae0035e894.js

132 ms

68088.add384c5b81191ea0307.js

68088.add384c5b81191ea0307.js

131 ms

88125.ad06fe4f7bc9a0da0652.js

88125.ad06fe4f7bc9a0da0652.js

118 ms

65310.e89d596fb22f7be8e2de.js

65310.e89d596fb22f7be8e2de.js

131 ms

78686.19cf9092d464087cf123.js

78686.19cf9092d464087cf123.js

131 ms

24664.f9fcc3ceb2af7967b5d3.js

24664.f9fcc3ceb2af7967b5d3.js

133 ms

25675-3285bc08083b22a528bd.js

25675-3285bc08083b22a528bd.js

132 ms

16359-f7720050668a08728530.js

16359-f7720050668a08728530.js

135 ms

97626.07e8a2f11ca3fb64e89b.js

97626.07e8a2f11ca3fb64e89b.js

133 ms

36864-9868dc164bb9b9384520.js

36864-9868dc164bb9b9384520.js

136 ms

36507.20c69ab03c9834ea3a26.js

36507.20c69ab03c9834ea3a26.js

139 ms

71809.f7d64e7f726817cc3014.js

71809.f7d64e7f726817cc3014.js

141 ms

94458.6266fd81bb2a9e1b5186.js

94458.6266fd81bb2a9e1b5186.js

141 ms

57721.55a1063df49bc0478154.js

57721.55a1063df49bc0478154.js

144 ms

97733-9a1d9676a0e0eeefe87c.js

97733-9a1d9676a0e0eeefe87c.js

152 ms

12889.373b5500bb8df390ebde.js

12889.373b5500bb8df390ebde.js

150 ms

21905-cef0d9af0ae073accb4e.js

21905-cef0d9af0ae073accb4e.js

151 ms

98799.3947646dd266c9c6003c.js

98799.3947646dd266c9c6003c.js

154 ms

57290.b796bfa6d6b136a5033f.js

57290.b796bfa6d6b136a5033f.js

156 ms

1571.dda2256ca05d7326d25b.js

1571.dda2256ca05d7326d25b.js

156 ms

80494.7519eac140daeac937de.js

80494.7519eac140daeac937de.js

163 ms

webpack-a49e5d22f39b590174a3.js

webpack-a49e5d22f39b590174a3.js

167 ms

framework-36d12d2979e5d3c3fd4b.js

framework-36d12d2979e5d3c3fd4b.js

168 ms

website-banner_3_hl.webp

website-banner_3_hl.webp

112 ms

main-17e94ee000bdd37d1e39.js

main-17e94ee000bdd37d1e39.js

86 ms

_app-c8be50c305cfd9986792.js

_app-c8be50c305cfd9986792.js

84 ms

1216-af9beff3dd9d98d8b12f.js

1216-af9beff3dd9d98d8b12f.js

79 ms

homePage-58928a3e960b4fb7fa3c.js

homePage-58928a3e960b4fb7fa3c.js

89 ms

_buildManifest.js

_buildManifest.js

89 ms

_ssgManifest.js

_ssgManifest.js

88 ms

css2

css2

309 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

353 ms

45788.4d400a5e93322b4a9ba4.js

45788.4d400a5e93322b4a9ba4.js

160 ms

12341.968f966bea476412a3b3.js

12341.968f966bea476412a3b3.js

168 ms

44092.3fddc8d7dfeda64156d7.js

44092.3fddc8d7dfeda64156d7.js

159 ms

bca6b26b9eb1bfa8286e.css

bca6b26b9eb1bfa8286e.css

152 ms

65525.4c6c48458162f6749ad3.js

65525.4c6c48458162f6749ad3.js

143 ms

30171.abf66190b3ddb52c67bd.js

30171.abf66190b3ddb52c67bd.js

139 ms

17cb68b2023f70f3c347.css

17cb68b2023f70f3c347.css

148 ms

92792.992e30273c3ce9ccb12b.js

92792.992e30273c3ce9ccb12b.js

154 ms

49093.1d01b6d7ff079d63d413.js

49093.1d01b6d7ff079d63d413.js

153 ms

27fc1e5c279df5b05e6f.css

27fc1e5c279df5b05e6f.css

119 ms

74636.93791113b448b34502fd.js

74636.93791113b448b34502fd.js

124 ms

83271.fbe1d67ddc100ed1811a.js

83271.fbe1d67ddc100ed1811a.js

121 ms

39258.cc6955b036cc45e0e62d.js

39258.cc6955b036cc45e0e62d.js

122 ms

5418456a55b94206fe25.css

5418456a55b94206fe25.css

141 ms

48023.0ad6d2ef3fe947ab127f.js

48023.0ad6d2ef3fe947ab127f.js

161 ms

f0c815ef5e4e5933e627.css

f0c815ef5e4e5933e627.css

137 ms

99893.6043282169661476d281.js

99893.6043282169661476d281.js

156 ms

ce8440a86bc49432bbad.css

ce8440a86bc49432bbad.css

91 ms

48404.eb29f6e9037d61b9885a.js

48404.eb29f6e9037d61b9885a.js

105 ms

10098.7698c2f2b16f92358ed1.js

10098.7698c2f2b16f92358ed1.js

105 ms

23b2023c.76a6bde7dcee990b5e76.js

23b2023c.76a6bde7dcee990b5e76.js

192 ms

99504.677824617be196571790.js

99504.677824617be196571790.js

69 ms

flags.png

flags.png

133 ms

S6uyw4BMUTPHvxk.ttf

S6uyw4BMUTPHvxk.ttf

75 ms

S6u9w4BMUTPHh7USew8.ttf

S6u9w4BMUTPHh7USew8.ttf

85 ms

S6u9w4BMUTPHh6UVew8.ttf

S6u9w4BMUTPHh6UVew8.ttf

147 ms

S6u9w4BMUTPHh50Xew8.ttf

S6u9w4BMUTPHh50Xew8.ttf

146 ms

banner200kb.webp

banner200kb.webp

69 ms

91033-9a668f01dc8aab6e0c19.js

91033-9a668f01dc8aab6e0c19.js

44 ms

46066-63e6ba1e533bc0ea6dd0.js

46066-63e6ba1e533bc0ea6dd0.js

53 ms

27710.596760f33837dbaa3983.js

27710.596760f33837dbaa3983.js

56 ms

9776.ac39e0e0f513a1d590d0.js

9776.ac39e0e0f513a1d590d0.js

41 ms

959c18964390b55d23d4.css

959c18964390b55d23d4.css

31 ms

25055.c1ac2e50a03e14406039.js

25055.c1ac2e50a03e14406039.js

30 ms

exitpopup_final_deskptop_2+copy.webp

exitpopup_final_deskptop_2+copy.webp

54 ms

Accessibility Review

homelane.com accessibility score

64

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

ARIA IDs are not unique

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

homelane.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

homelane.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Homelane.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 Homelane.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.

Social Sharing Optimization

homelane.com

Open Graph data is detected on the main page of Home Lane. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: