Tools & Wizards About Us
indusre.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

indusre.com

Indus Real Estate LLC | Dubai Luxury Properties

Page Load Speed

3.1 sec in total

First Response

241 ms

Resources Loaded

2.1 sec

Page Rendered

707 ms

indusre.com screenshot

About Website

Welcome to indusre.com homepage info - get ready to check Indus Re best content right away, or after learning these important things about indusre.com

Visit indusre.com

Key Findings

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

Performance Metrics

indusre.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

Network Requests Diagram

indusre.com

241 ms

b7e43fe594d1494d.css

12 ms

7fd2ed82bbca1342.css

59 ms

b1c7906582135473.css

11 ms

14db44f84aed9860.css

10 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 95% of them (52 requests) were addressed to the original Indusre.com, 5% (3 requests) were made to Indusspeciality.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Indusspeciality.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.9 kB (6%)

Content Size

3.2 MB

After Optimization

3.0 MB

  • HTML
  • Images

In fact, the total size of Indusre.com main page is 3.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 191.9 kB

  • Original 212.1 kB
  • After minification 211.8 kB
  • After compression 20.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. 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 191.9 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 22 B

  • Original 3.0 MB
  • After minification 3.0 MB

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. Indus Re images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 23 (48%)

Requests Now

48

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indusre.com

indusre.com

241 ms

b7e43fe594d1494d.css

b7e43fe594d1494d.css

12 ms

7fd2ed82bbca1342.css

7fd2ed82bbca1342.css

59 ms

b1c7906582135473.css

b1c7906582135473.css

11 ms

14db44f84aed9860.css

14db44f84aed9860.css

10 ms

fd9d1056-0787554314ba2b7c.js

fd9d1056-0787554314ba2b7c.js

18 ms

2472-d5583b65c5130509.js

2472-d5583b65c5130509.js

23 ms

main-app-b9a07df335b481c1.js

main-app-b9a07df335b481c1.js

15 ms

layout-6cccb3743fbc5259.js

layout-6cccb3743fbc5259.js

17 ms

46170725-d2455a27d55390be.js

46170725-d2455a27d55390be.js

22 ms

1353-64670eccfe4a5db2.js

1353-64670eccfe4a5db2.js

33 ms

2173-c5c12bb3fa05572b.js

2173-c5c12bb3fa05572b.js

25 ms

2145-0d220b97a830145c.js

2145-0d220b97a830145c.js

29 ms

7641-efa04caacc5a1d0f.js

7641-efa04caacc5a1d0f.js

29 ms

9419-ded70165096d08d6.js

9419-ded70165096d08d6.js

27 ms

38-ce14391282729c04.js

38-ce14391282729c04.js

31 ms

4568-aeb706896a06239e.js

4568-aeb706896a06239e.js

32 ms

3741-0cc66ba7f1191569.js

3741-0cc66ba7f1191569.js

34 ms

743-0c6241abf3b3d436.js

743-0c6241abf3b3d436.js

35 ms

7354-3b50a40c6a810ae1.js

7354-3b50a40c6a810ae1.js

45 ms

5938-9abffc59b6268d8e.js

5938-9abffc59b6268d8e.js

39 ms

3785-963e1651c9c3c0e0.js

3785-963e1651c9c3c0e0.js

40 ms

9819-637099d5df10c89a.js

9819-637099d5df10c89a.js

42 ms

page-d3d55dee1dd98d8f.js

page-d3d55dee1dd98d8f.js

39 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

47 ms

webpack-a97afe442878c17b.js

webpack-a97afe442878c17b.js

42 ms

whatsapp.svg

whatsapp.svg

1596 ms

mobile-dark-nav-icon.svg

mobile-dark-nav-icon.svg

131 ms

google_logo.svg

google_logo.svg

132 ms

image

image

130 ms

image

image

130 ms

image

image

132 ms

image

image

133 ms

image

image

133 ms

image

image

134 ms

image

image

140 ms

image

image

140 ms

image

image

140 ms

image

image

144 ms

image

image

157 ms

image

image

152 ms

image

image

150 ms

image

image

150 ms

image

image

151 ms

image

image

156 ms

image

image

161 ms

image

image

165 ms

image

image

225 ms

image

image

163 ms

flaticon_realton60b2.1bd6cbb8.ttf

flaticon_realton60b2.1bd6cbb8.ttf

81 ms

fa-regular-400.9f10997b.woff

fa-regular-400.9f10997b.woff

141 ms

fa-light-300.3631ce7f.woff

fa-light-300.3631ce7f.woff

142 ms

fa-thin-100.e2e9c603.woff

fa-thin-100.e2e9c603.woff

142 ms

fa-solid-900.25fc0d49.woff

fa-solid-900.25fc0d49.woff

142 ms

fa-brands-400.71dfaf1a.woff

fa-brands-400.71dfaf1a.woff

140 ms

Accessibility Review

indusre.com accessibility score

75

Accessibility Issues

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Heading elements are not in a sequentially-descending order

Best Practices

indusre.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

SEO Factors

indusre.com SEO score

85

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

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

indusre.com

Open Graph description is not detected on the main page of Indus Re. 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: