Tools & Wizards About Us
lilypadwedding.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

lilypadwedding.com

Buffalo, NY Wedding and Event Planners | Gift Boutique

Page Load Speed

1.9 sec in total

First Response

162 ms

Resources Loaded

1.7 sec

Page Rendered

76 ms

lilypadwedding.com screenshot

About Website

Click here to check amazing Lilypad Wedding content. Otherwise, check out these important facts you probably never knew about lilypadwedding.com

Corporate Event Planning, Wedding Day Coordinators, Custom Wedding and Event Planning, Invitation and Event Design, Unique Gifts, stationery and notecards

Visit lilypadwedding.com

Key Findings

We analyzed Lilypadwedding.com page load time and found that the first response time was 162 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

lilypadwedding.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

lilypadwedding.com

162 ms

www.lilypadwedding.com

626 ms

require.min.js

52 ms

main-r.min.js

54 ms

bt

181 ms

Our browser made a total of 160 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Lilypadwedding.com, 94% (150 requests) were made to Static.parastorage.com and 3% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (745 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 689.5 kB (62%)

Content Size

1.1 MB

After Optimization

420.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Lilypadwedding.com main page is 1.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. 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. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 67.0 kB

  • Original 84.5 kB
  • After minification 84.3 kB
  • After compression 17.5 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 67.0 kB or 79% of the original size.

JavaScript Optimization

-61%

Potential reduce by 621.9 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 389.4 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 621.9 kB or 61% of the original size.

CSS Optimization

-4%

Potential reduce by 557 B

  • Original 13.9 kB
  • After minification 13.9 kB
  • After compression 13.4 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. Lilypadwedding.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 148 (94%)

Requests Now

158

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lilypadwedding.com

lilypadwedding.com

162 ms

www.lilypadwedding.com

www.lilypadwedding.com

626 ms

require.min.js

require.min.js

52 ms

main-r.min.js

main-r.min.js

54 ms

bt

bt

181 ms

990aea_8e0bd0872330511e218bbce1ae0a13b7_232.json.z

990aea_8e0bd0872330511e218bbce1ae0a13b7_232.json.z

425 ms

990aea_01154e212ed1b11bd858b6f3ace68bc2_235.json.z

990aea_01154e212ed1b11bd858b6f3ace68bc2_235.json.z

745 ms

ugc-viewer

ugc-viewer

108 ms

bt

bt

112 ms

react-with-addons.min.js

react-with-addons.min.js

23 ms

lodash.min.js

lodash.min.js

21 ms

wixCodeInit.min.js

wixCodeInit.min.js

20 ms

coreUtils.js

coreUtils.js

41 ms

coreUtils.min.js

coreUtils.min.js

40 ms

skins.min.js

skins.min.js

99 ms

components.min.js

components.min.js

77 ms

core.min.js

core.min.js

98 ms

mobx.umd.min.js

mobx.umd.min.js

76 ms

mobx-react.min.js

mobx-react.min.js

97 ms

TweenMax.min.js

TweenMax.min.js

99 ms

animations.min.js

animations.min.js

101 ms

react-with-addons.min.js

react-with-addons.min.js

102 ms

layout.min.js

layout.min.js

100 ms

wixappsCore.min.js

wixappsCore.min.js

101 ms

wixappsClassics.min.js

wixappsClassics.min.js

249 ms

container.min.js

container.min.js

274 ms

imageZoom.min.js

imageZoom.min.js

275 ms

mediaZoom.min.js

mediaZoom.min.js

275 ms

imageZoomDisplayer.min.js

imageZoomDisplayer.min.js

275 ms

matrixGallery.min.js

matrixGallery.min.js

273 ms

slideShowGallery.min.js

slideShowGallery.min.js

275 ms

comboBoxInput.min.js

comboBoxInput.min.js

275 ms

dialogs.min.js

dialogs.min.js

277 ms

table.min.js

table.min.js

277 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

274 ms

tpa.min.js

tpa.min.js

277 ms

dataFixer.min.js

dataFixer.min.js

277 ms

siteUtils.min.js

siteUtils.min.js

276 ms

image.min.js

image.min.js

281 ms

balata.min.js

balata.min.js

278 ms

translationsUtils.min.js

translationsUtils.min.js

279 ms

hammer.min.js

hammer.min.js

279 ms

utils.min.js

utils.min.js

276 ms

fonts.min.js

fonts.min.js

276 ms

platformUtils-bundle.js

platformUtils-bundle.js

279 ms

loggingUtils.min.js

loggingUtils.min.js

276 ms

imageClientApi.js

imageClientApi.js

274 ms

swfobject.min.js

swfobject.min.js

276 ms

santaProps.min.js

santaProps.min.js

255 ms

displayer.min.js

displayer.min.js

255 ms

mousetrap.min.js

mousetrap.min.js

217 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

214 ms

react-dom.min.js

react-dom.min.js

198 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

200 ms

widgets.min.js

widgets.min.js

199 ms

react-dom-server.min.js

react-dom-server.min.js

194 ms

imageCommon.min.js

imageCommon.min.js

195 ms

formCommon.min.js

formCommon.min.js

195 ms

textCommon.min.js

textCommon.min.js

195 ms

containerCommon.min.js

containerCommon.min.js

47 ms

socialCommon.min.js

socialCommon.min.js

117 ms

galleriesCommon.min.js

galleriesCommon.min.js

115 ms

buttonCommon.min.js

buttonCommon.min.js

116 ms

compDesignUtils.min.js

compDesignUtils.min.js

115 ms

mediaCommon.min.js

mediaCommon.min.js

115 ms

audioCommon.min.js

audioCommon.min.js

115 ms

skinExports.min.js

skinExports.min.js

114 ms

compUtils.min.js

compUtils.min.js

115 ms

mobileLayoutUtils.js

mobileLayoutUtils.js

114 ms

pm-rpc.min.js

pm-rpc.min.js

114 ms

tweenEngine.min.js

tweenEngine.min.js

113 ms

multilingual.min.js

multilingual.min.js

114 ms

render.min.js

render.min.js

113 ms

color.min.js

color.min.js

113 ms

zepto.min.js

zepto.min.js

113 ms

xss.min.js

xss.min.js

112 ms

bluebird.min.js

bluebird.min.js

112 ms

imageClientApi.min.js

imageClientApi.min.js

112 ms

column.min.js

column.min.js

112 ms

siteBackground.min.js

siteBackground.min.js

111 ms

hoverBox.min.js

hoverBox.min.js

111 ms

mediaContainerFactory.min.js

mediaContainerFactory.min.js

111 ms

internalMarkings.min.js

internalMarkings.min.js

110 ms

repeater.min.js

repeater.min.js

110 ms

zoomedImage.min.js

zoomedImage.min.js

110 ms

menuButton.min.js

menuButton.min.js

110 ms

messageView.min.js

messageView.min.js

109 ms

backgroundCommon.min.js

backgroundCommon.min.js

66 ms

bt

bt

122 ms

css

css

32 ms

TweenMax.min.js

TweenMax.min.js

29 ms

svgShape.min.js

svgShape.min.js

15 ms

adminLoginButton.min.js

adminLoginButton.min.js

17 ms

wTwitterFollow.min.js

wTwitterFollow.min.js

16 ms

facebookComments.min.js

facebookComments.min.js

18 ms

verticalAnchorsMenu.min.js

verticalAnchorsMenu.min.js

19 ms

facebookShare.min.js

facebookShare.min.js

17 ms

vKShareButton.min.js

vKShareButton.min.js

20 ms

youTubeSubscribeButton.min.js

youTubeSubscribeButton.min.js

19 ms

itunesButton.min.js

itunesButton.min.js

19 ms

skypeCallButton.min.js

skypeCallButton.min.js

20 ms

fileUploader.min.js

fileUploader.min.js

20 ms

pinItPinWidget.min.js

pinItPinWidget.min.js

22 ms

popupCloseTextButton.min.js

popupCloseTextButton.min.js

22 ms

radioButton.min.js

radioButton.min.js

20 ms

radioGroup.min.js

radioGroup.min.js

21 ms

documentMedia.min.js

documentMedia.min.js

22 ms

datePicker.min.js

datePicker.min.js

22 ms

contactForm.min.js

contactForm.min.js

24 ms

subscribeForm.min.js

subscribeForm.min.js

22 ms

textArea.min.js

textArea.min.js

23 ms

loginSocialBar.min.js

loginSocialBar.min.js

27 ms

googleMap.min.js

googleMap.min.js

23 ms

soundCloudWidget.min.js

soundCloudWidget.min.js

24 ms

paypalButton.min.js

paypalButton.min.js

24 ms

imageButton.min.js

imageButton.min.js

26 ms

linkBar.min.js

linkBar.min.js

24 ms

spotifyPlayer.min.js

spotifyPlayer.min.js

25 ms

spotifyFollow.min.js

spotifyFollow.min.js

26 ms

twitterFeed.min.js

twitterFeed.min.js

27 ms

backToTopButton.min.js

backToTopButton.min.js

28 ms

svgCommon.min.js

svgCommon.min.js

26 ms

facebookLike.min.js

facebookLike.min.js

28 ms

facebookLikeBox.min.js

facebookLikeBox.min.js

29 ms

flickrBadgeWidget.min.js

flickrBadgeWidget.min.js

27 ms

rssButton.min.js

rssButton.min.js

28 ms

tinyMenu.min.js

tinyMenu.min.js

43 ms

groupContainer.min.js

groupContainer.min.js

43 ms

wGooglePlusOne.min.js

wGooglePlusOne.min.js

43 ms

pinterestPinIt.min.js

pinterestPinIt.min.js

43 ms

pinterestFollow.min.js

pinterestFollow.min.js

41 ms

wTwitterTweet.min.js

wTwitterTweet.min.js

41 ms

audioPlayer.min.js

audioPlayer.min.js

41 ms

loginButton.min.js

loginButton.min.js

41 ms

htmlComponent.min.js

htmlComponent.min.js

40 ms

deadComponent.min.js

deadComponent.min.js

40 ms

mediaPlayer.min.js

mediaPlayer.min.js

41 ms

mediaControls.min.js

mediaControls.min.js

41 ms

singleAudioPlayer.min.js

singleAudioPlayer.min.js

39 ms

quickActionBar.min.js

quickActionBar.min.js

40 ms

boxSlideShowSlide.min.js

boxSlideShowSlide.min.js

40 ms

stripSlideShowSlide.min.js

stripSlideShowSlide.min.js

40 ms

page.min.js

page.min.js

39 ms

bgImageStrip.min.js

bgImageStrip.min.js

39 ms

popupContainer.min.js

popupContainer.min.js

38 ms

stripContainer.min.js

stripContainer.min.js

38 ms

stripColumnsContainer.min.js

stripColumnsContainer.min.js

38 ms

exitMobileModeButton.min.js

exitMobileModeButton.min.js

38 ms

tpaGalleries.min.js

tpaGalleries.min.js

37 ms

flashComponent.min.js

flashComponent.min.js

38 ms

stripSlideShow.min.js

stripSlideShow.min.js

37 ms

mobileActionsMenu.min.js

mobileActionsMenu.min.js

37 ms

verticalMenu.min.js

verticalMenu.min.js

37 ms

disqusComments.min.js

disqusComments.min.js

36 ms

checkbox.min.js

checkbox.min.js

36 ms

gridComponent.min.js

gridComponent.min.js

37 ms

languageSelector.min.js

languageSelector.min.js

35 ms

lodash.min.js

lodash.min.js

39 ms

bt

bt

21 ms

languages.css

languages.css

43 ms

Accessibility Review

lilypadwedding.com accessibility score

89

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

Best Practices

lilypadwedding.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

lilypadwedding.com SEO score

89

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilypadwedding.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lilypadwedding.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

lilypadwedding.com

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