Tools & Wizards About Us
olivestree.in screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

olivestree.in

Wedding Planner in Lucknow | Luxury Wedding Planner in Lucknow | Wedding Decorators in Lucknow

Page Load Speed

3.1 sec in total

First Response

300 ms

Resources Loaded

1.6 sec

Page Rendered

1.2 sec

olivestree.in screenshot

About Website

Welcome to olivestree.in homepage info - get ready to check Olivestree best content for India right away, or after learning these important things about olivestree.in

Our goal is to create a wedding that encompasses everything you love as a couple and leave your guests with unforgettable memories. As wedding planning experts, we can also plan corporate and social e...

Visit olivestree.in

Key Findings

We analyzed Olivestree.in page load time and found that the first response time was 300 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

olivestree.in performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.381

27/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

olivestree.in

300 ms

bootstrap.min.css

118 ms

animate.css

128 ms

jquery-ui.min.css

126 ms

meanmenu.min.css

124 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 92% of them (98 requests) were addressed to the original Olivestree.in, 5% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (617 ms) belongs to the original domain Olivestree.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 196.3 kB (3%)

Content Size

6.0 MB

After Optimization

5.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Olivestree.in main page is 6.0 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. 75% 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 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 56.0 kB

  • Original 64.5 kB
  • After minification 39.7 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 24.8 kB, which is 38% 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 56.0 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 86.8 kB

  • Original 5.8 MB
  • After minification 5.7 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. Olivestree images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 25.4 kB

  • Original 100.7 kB
  • After minification 100.7 kB
  • After compression 75.3 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 25.4 kB or 25% of the original size.

CSS Optimization

-39%

Potential reduce by 28.1 kB

  • Original 71.9 kB
  • After minification 71.7 kB
  • After compression 43.8 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. Olivestree.in needs all CSS files to be minified and compressed as it can save up to 28.1 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (25%)

Requests Now

97

After Optimization

73

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

olivestree.in

olivestree.in

300 ms

bootstrap.min.css

bootstrap.min.css

118 ms

animate.css

animate.css

128 ms

jquery-ui.min.css

jquery-ui.min.css

126 ms

meanmenu.min.css

meanmenu.min.css

124 ms

owl.carousel.css

owl.carousel.css

126 ms

font-awesome.min.css

font-awesome.min.css

129 ms

nivo-slider.css

nivo-slider.css

177 ms

preview.css

preview.css

180 ms

style.css

style.css

179 ms

style.css

style.css

242 ms

responsive.css

responsive.css

181 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

184 ms

js

js

84 ms

jquery-1.12.0.min.js

jquery-1.12.0.min.js

196 ms

bootstrap.min.js

bootstrap.min.js

396 ms

owl.carousel.min.js

owl.carousel.min.js

191 ms

jquery.meanmenu.js

jquery.meanmenu.js

200 ms

jquery-ui.min.js

jquery-ui.min.js

201 ms

wow.min.js

wow.min.js

394 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

395 ms

home.js

home.js

395 ms

jquery.gallery.js

jquery.gallery.js

396 ms

modernizr.custom.53451

modernizr.custom.53451

399 ms

plugins.js

plugins.js

397 ms

main.js

main.js

396 ms

css

css

30 ms

css

css

48 ms

logo.png

logo.png

121 ms

slide1.jpg

slide1.jpg

314 ms

slide2.jpg

slide2.jpg

236 ms

slide3.jpg

slide3.jpg

268 ms

section-line.png

section-line.png

122 ms

bg.png

bg.png

125 ms

service1.png

service1.png

146 ms

service2.png

service2.png

234 ms

service3.png

service3.png

235 ms

about-feature.png

about-feature.png

428 ms

service-bg.jpg

service-bg.jpg

260 ms

1.png

1.png

261 ms

3.png

3.png

261 ms

10.png

10.png

319 ms

9.png

9.png

322 ms

11.png

11.png

323 ms

12.png

12.png

326 ms

7.png

7.png

376 ms

13.png

13.png

379 ms

8.png

8.png

380 ms

2.png

2.png

382 ms

4.png

4.png

386 ms

14.png

14.png

437 ms

6.png

6.png

439 ms

15.png

15.png

439 ms

5.png

5.png

441 ms

banner.png

banner.png

617 ms

left.png

left.png

487 ms

right.png

right.png

390 ms

browser.png

browser.png

385 ms

1.jpg

1.jpg

442 ms

2.jpg

2.jpg

388 ms

3.jpg

3.jpg

433 ms

4.jpg

4.jpg

501 ms

5.jpg

5.jpg

447 ms

6.jpg

6.jpg

447 ms

7.jpg

7.jpg

494 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

37 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

37 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rm.ttf

111 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

113 ms

SZc83FzrJKuqFbwMKk6EhUXz6A.ttf

SZc83FzrJKuqFbwMKk6EhUXz6A.ttf

114 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

553 ms

8.jpg

8.jpg

483 ms

bg.jpg

bg.jpg

471 ms

team-bg.png

team-bg.png

442 ms

1.png

1.png

456 ms

2.png

2.png

501 ms

3.png

3.png

484 ms

1.jpg

1.jpg

447 ms

2.jpg

2.jpg

473 ms

3.jpg

3.jpg

470 ms

4.jpg

4.jpg

430 ms

5.jpg

5.jpg

432 ms

6.jpg

6.jpg

477 ms

7.jpg

7.jpg

474 ms

8.jpg

8.jpg

474 ms

add.jpg

add.jpg

427 ms

bg.png

bg.png

539 ms

1.png

1.png

434 ms

2.png

2.png

477 ms

3.png

3.png

474 ms

4.png

4.png

436 ms

bg.jpg

bg.jpg

428 ms

1.jpg

1.jpg

437 ms

2.jpg

2.jpg

481 ms

3.jpg

3.jpg

479 ms

bg.jpg

bg.jpg

436 ms

footer-logo.png

footer-logo.png

424 ms

whatsaap-circle.png

whatsaap-circle.png

433 ms

facebook-circle.png

facebook-circle.png

474 ms

instagram-circle.png

instagram-circle.png

430 ms

twitter-circle.png

twitter-circle.png

423 ms

gplus-circle.png

gplus-circle.png

418 ms

linkedin-circle.png

linkedin-circle.png

419 ms

youtube-circle.png

youtube-circle.png

384 ms

slide-border.png

slide-border.png

422 ms

love.png

love.png

422 ms

Accessibility Review

olivestree.in accessibility score

71

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.

High

[role]s are not contained by their required parent element

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

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

olivestree.in best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

olivestree.in SEO score

81

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

olivestree.in

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