Tools & Wizards About Us
ebuild.in screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ebuild.in

eBuild India's Architecture, Art, Design & Construction

Page Load Speed

5.8 sec in total

First Response

467 ms

Resources Loaded

4.7 sec

Page Rendered

627 ms

ebuild.in screenshot

About Website

Visit ebuild.in now to see the best up-to-date EBuild content for India and also check out these interesting facts you probably never knew about ebuild.in

ebuild is the smart way to design home. Browse Products, Materials, Brands, Professionals, Home decor design ideas and photos, Retailers, Events in ebuild.in

Visit ebuild.in

Key Findings

We analyzed Ebuild.in page load time and found that the first response time was 467 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ebuild.in performance score

0

Network Requests Diagram

ebuild.in

467 ms

bootstrap.min.css

308 ms

font-awesome.min.css

136 ms

site1.min.css

453 ms

home.min.css

163 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 93% of them (50 requests) were addressed to the original Ebuild.in, 4% (2 requests) were made to Apis.google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Ebuild.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 316.2 kB (50%)

Content Size

637.0 kB

After Optimization

320.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ebuild.in main page is 637.0 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. 50% of websites need less resources to load. CSS take 233.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 42.2 kB

  • Original 51.3 kB
  • After minification 41.8 kB
  • After compression 9.2 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 9.5 kB, which is 19% 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 42.2 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 8.6 kB

  • Original 160.1 kB
  • After minification 151.5 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. EBuild images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 117.7 kB

  • Original 191.9 kB
  • After minification 191.9 kB
  • After compression 74.2 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 117.7 kB or 61% of the original size.

CSS Optimization

-63%

Potential reduce by 147.7 kB

  • Original 233.6 kB
  • After minification 233.5 kB
  • After compression 85.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. Ebuild.in needs all CSS files to be minified and compressed as it can save up to 147.7 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (22%)

Requests Now

50

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ebuild.in

ebuild.in

467 ms

bootstrap.min.css

bootstrap.min.css

308 ms

font-awesome.min.css

font-awesome.min.css

136 ms

site1.min.css

site1.min.css

453 ms

home.min.css

home.min.css

163 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

430 ms

enum.min.js

enum.min.js

170 ms

jquery-ui-1.10.4.custom.min.js

jquery-ui-1.10.4.custom.min.js

101 ms

bootstrap.min.js

bootstrap.min.js

148 ms

site1.js

site1.js

217 ms

homepage.min.js

homepage.min.js

150 ms

plusone.js

plusone.js

221 ms

ebuild.png

ebuild.png

159 ms

815.jpg

815.jpg

154 ms

817.jpg

817.jpg

152 ms

599.jpg

599.jpg

149 ms

757.jpg

757.jpg

150 ms

imksp66778_200_265_1-good-homes.jpg

imksp66778_200_265_1-good-homes.jpg

152 ms

imksp66567_200_265_1-architectural-digest.jpg

imksp66567_200_265_1-architectural-digest.jpg

191 ms

imksp66619_200_265_1-architect-and-interiors.jpg

imksp66619_200_265_1-architect-and-interiors.jpg

671 ms

imksp66623_200_265_1-construction-world.jpg

imksp66623_200_265_1-construction-world.jpg

1182 ms

imksp66627_200_265_1-good-housekeeping.jpg

imksp66627_200_265_1-good-housekeeping.jpg

3253 ms

imksp66616_200_265_1-pool.jpg

imksp66616_200_265_1-pool.jpg

2739 ms

imksp14302_310_200_1-ashoka-universal-high-school.jpg

imksp14302_310_200_1-ashoka-universal-high-school.jpg

3827 ms

1.jpg

1.jpg

280 ms

imksp10479_310_200_1-it-towers-at-mindspace-malad.jpg

imksp10479_310_200_1-it-towers-at-mindspace-malad.jpg

352 ms

413.jpg

413.jpg

414 ms

imksp3079_310_200_1-hospitality.jpg

imksp3079_310_200_1-hospitality.jpg

521 ms

91.jpg

91.jpg

581 ms

imksp12714_310_200_1-lifestyle.jpg

imksp12714_310_200_1-lifestyle.jpg

2244 ms

16.jpg

16.jpg

723 ms

imksp247_310_200_1-hyatt-regency.jpg

imksp247_310_200_1-hyatt-regency.jpg

810 ms

52.jpg

52.jpg

864 ms

imksp15000_310_200_1-salt-lake-city-centre.jpg

imksp15000_310_200_1-salt-lake-city-centre.jpg

946 ms

67.jpg

67.jpg

998 ms

imksp7980_310_200_1-toto-showroom.jpg

imksp7980_310_200_1-toto-showroom.jpg

1080 ms

303.jpg

303.jpg

1146 ms

imksp15546_310_200_1-architectural-portraits.jpg

imksp15546_310_200_1-architectural-portraits.jpg

1253 ms

203.jpg

203.jpg

1248 ms

102.jpg

102.jpg

1296 ms

302.jpg

302.jpg

1299 ms

108.jpg

108.jpg

1342 ms

118.jpg

118.jpg

1351 ms

space-planning-and-design-ideas-for-kids-room-decor.jpg

space-planning-and-design-ideas-for-kids-room-decor.jpg

1523 ms

kids-room-decor-dos-and-donts-to-keep-in-mind.jpg

kids-room-decor-dos-and-donts-to-keep-in-mind.jpg

1997 ms

get-structured-before-the-big-shift.jpg

get-structured-before-the-big-shift.jpg

1696 ms

latest-creative-rangoli-design-ideas-to-try-this-festive-season.jpg

latest-creative-rangoli-design-ideas-to-try-this-festive-season.jpg

1799 ms

ebuild.jpg

ebuild.jpg

1972 ms

Noto-Sans-700.ttf

Noto-Sans-700.ttf

1902 ms

Noto-Sans-regular.ttf

Noto-Sans-regular.ttf

1942 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1963 ms

ga.js

ga.js

30 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

43 ms

__utm.gif

__utm.gif

41 ms

SEO Factors

ebuild.in SEO score

0

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 Ebuild.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 Ebuild.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.

Social Sharing Optimization

ebuild.in

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