Tools & Wizards About Us
vanshikaweddingplanner.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

vanshikaweddingplanner.com

Wedding Caterer, Planner in Lucknow | Wedding Venue in Lucknow

Page Load Speed

3.4 sec in total

First Response

195 ms

Resources Loaded

2.5 sec

Page Rendered

673 ms

vanshikaweddingplanner.com screenshot

About Website

Welcome to vanshikaweddingplanner.com homepage info - get ready to check Vanshika Wedding Planner best content for India right away, or after learning these important things about vanshikaweddingplanner.com

Vanshika Wedding Planner Provide wedding Catering, wedding venue, wedding photography and bridal makeup in Lucknow Contact us for best wedding planner in Lucknow.

Visit vanshikaweddingplanner.com

Key Findings

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

Performance Metrics

vanshikaweddingplanner.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.316

37/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

vanshikaweddingplanner.com

195 ms

vanshikaweddingplanner.com

248 ms

www.vanshikaweddingplanner.com

250 ms

www.vanshikaweddingplanner.com

316 ms

tooltipster9b70.css

120 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 83% of them (85 requests) were addressed to the original Vanshikaweddingplanner.com, 8% (8 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (838 ms) belongs to the original domain Vanshikaweddingplanner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 239.7 kB (8%)

Content Size

3.1 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vanshikaweddingplanner.com main page is 3.1 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 92.7 kB

  • Original 115.6 kB
  • After minification 111.0 kB
  • After compression 22.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 92.7 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 3.1 kB

  • Original 2.4 MB
  • After minification 2.4 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. Vanshika Wedding Planner images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 74.0 kB

  • Original 353.0 kB
  • After minification 353.0 kB
  • After compression 279.0 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 74.0 kB or 21% of the original size.

CSS Optimization

-34%

Potential reduce by 70.0 kB

  • Original 206.0 kB
  • After minification 205.8 kB
  • After compression 136.0 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. Vanshikaweddingplanner.com needs all CSS files to be minified and compressed as it can save up to 70.0 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (61%)

Requests Now

87

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vanshikaweddingplanner.com

vanshikaweddingplanner.com

195 ms

vanshikaweddingplanner.com

vanshikaweddingplanner.com

248 ms

www.vanshikaweddingplanner.com

www.vanshikaweddingplanner.com

250 ms

www.vanshikaweddingplanner.com

www.vanshikaweddingplanner.com

316 ms

tooltipster9b70.css

tooltipster9b70.css

120 ms

tooltipster-light9b70.css

tooltipster-light9b70.css

181 ms

animations02d2.css

animations02d2.css

183 ms

styles02d2.css

styles02d2.css

239 ms

responsive02d2.css

responsive02d2.css

181 ms

settingse24f.css

settingse24f.css

185 ms

css

css

22 ms

css

css

31 ms

css

css

28 ms

settings00d1.css

settings00d1.css

186 ms

woocommerce-layout459e.css

woocommerce-layout459e.css

241 ms

woocommerce459e.css

woocommerce459e.css

298 ms

style66f2.css

style66f2.css

243 ms

css

css

28 ms

fontello.css

fontello.css

244 ms

style.css

style.css

310 ms

core.animation.css

core.animation.css

303 ms

theme.shortcodes.css

theme.shortcodes.css

362 ms

theme.css

theme.css

376 ms

plugin.booked.css

plugin.booked.css

307 ms

responsive.css

responsive.css

370 ms

jquery.js

jquery.js

425 ms

jquery-migrate.js

jquery-migrate.js

423 ms

lightbox.js

lightbox.js

422 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

486 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

448 ms

modernizr.min.js

modernizr.min.js

444 ms

slider.css

slider.css

444 ms

slider.js

slider.js

445 ms

css

css

23 ms

jssor.slider-28.0.0.min.js

jssor.slider-28.0.0.min.js

524 ms

jssor.slider.min.js

jssor.slider.min.js

483 ms

swiper.css

swiper.css

482 ms

lightboxe24f.css

lightboxe24f.css

481 ms

core.messages.css

core.messages.css

483 ms

core.min.js

core.min.js

514 ms

datepicker.min.js

datepicker.min.js

514 ms

trx_utils.js

trx_utils.js

521 ms

js.cookie.js

js.cookie.js

553 ms

cart-fragments.js

cart-fragments.js

553 ms

superfish.js

superfish.js

554 ms

core.utils.js

core.utils.js

537 ms

core.init.js

core.init.js

473 ms

theme.init.js

theme.init.js

473 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

474 ms

wp-mediaelement.js

wp-mediaelement.js

469 ms

core.debug.js

core.debug.js

473 ms

wp-embed.js

wp-embed.js

491 ms

theme.shortcodes.js

theme.shortcodes.js

490 ms

js_composer_front.min.js

js_composer_front.min.js

489 ms

swiper.js

swiper.js

486 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

429 ms

jquery.themepunch.essential.min.js

jquery.themepunch.essential.min.js

433 ms

core.messages.js

core.messages.js

443 ms

logo1.png

logo1.png

257 ms

logo.png

logo.png

254 ms

spin.svg

spin.svg

254 ms

slider1.jpg

slider1.jpg

486 ms

slider2.jpg

slider2.jpg

619 ms

slider3.jpg

slider3.jpg

486 ms

bg_services.jpg

bg_services.jpg

484 ms

kanahiya.jpg

kanahiya.jpg

483 ms

manoj.jpg

manoj.jpg

483 ms

sumit.jpg

sumit.jpg

484 ms

blank.jpg

blank.jpg

540 ms

gal1.jpg

gal1.jpg

540 ms

gal2.jpg

gal2.jpg

539 ms

gal5.jpg

gal5.jpg

486 ms

gal3.jpg

gal3.jpg

537 ms

gal4.jpg

gal4.jpg

555 ms

1.jpg

1.jpg

526 ms

3.jpg

3.jpg

525 ms

EJRVQgYoZZY2vCFuvAFYzro.ttf

EJRVQgYoZZY2vCFuvAFYzro.ttf

40 ms

EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf

EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf

41 ms

EJRSQgYoZZY2vCFuvAnt66qcVy4.ttf

EJRSQgYoZZY2vCFuvAnt66qcVy4.ttf

42 ms

fontellod826.woff

fontellod826.woff

524 ms

title_bg_green.png

title_bg_green.png

59 ms

4.jpg

4.jpg

547 ms

bg2.jpg

bg2.jpg

155 ms

title_bg_white.png

title_bg_white.png

47 ms

main_bg.jpg

main_bg.jpg

46 ms

5.jpg

5.jpg

546 ms

6.jpg

6.jpg

546 ms

7.jpg

7.jpg

510 ms

contact.png

contact.png

838 ms

hompage-about-bg.jpg

hompage-about-bg.jpg

507 ms

story_img.jpg

story_img.jpg

643 ms

bg2.jpg

bg2.jpg

552 ms

loading.gif

loading.gif

553 ms

www.vanshikaweddingplanner.com

www.vanshikaweddingplanner.com

303 ms

loader.gif

loader.gif

203 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

22 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

22 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

23 ms

egfontdde9.woff

egfontdde9.woff

211 ms

woocommerce-smallscreen459e.css

woocommerce-smallscreen459e.css

66 ms

Accessibility Review

vanshikaweddingplanner.com accessibility score

65

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

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

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

vanshikaweddingplanner.com best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

vanshikaweddingplanner.com SEO score

73

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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

vanshikaweddingplanner.com

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