Tools & Wizards About Us
lizzyrob.wedding screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lizzyrob.wedding

Page Load Speed

3 sec in total

First Response

102 ms

Resources Loaded

2.3 sec

Page Rendered

640 ms

lizzyrob.wedding screenshot

About Website

Welcome to lizzyrob.wedding homepage info - get ready to check Lizzyrob best content right away, or after learning these important things about lizzyrob.wedding

Welcome to Elizabeth Erekosima and Robert Udah's Wedding Website! View photos, directions, registry details and more at The Knot.

Visit lizzyrob.wedding

Key Findings

We analyzed Lizzyrob.wedding page load time and found that the first response time was 102 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

lizzyrob.wedding performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value31,040 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value39.9 s

0/100

10%

Network Requests Diagram

lizzyrob.wedding

102 ms

www.lizzyrob.wedding

471 ms

consented-segment.js

62 ms

30498a168aaec04a.css

97 ms

polyfills-5cd94c89d3acac5f.js

131 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Lizzyrob.wedding, 50% (12 requests) were made to Static.theknot.com and 13% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Theknot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.1 kB (19%)

Content Size

632.3 kB

After Optimization

510.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lizzyrob.wedding main page is 632.3 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. 40% of websites need less resources to load. Images take 515.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 74.9 kB

  • Original 98.9 kB
  • After minification 98.8 kB
  • After compression 24.0 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 74.9 kB or 76% of the original size.

Image Optimization

-9%

Potential reduce by 45.0 kB

  • Original 515.8 kB
  • After minification 470.8 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. Lizzyrob images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 340 B

  • Original 14.7 kB
  • After minification 14.7 kB
  • After compression 14.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. This website has mostly compressed JavaScripts.

CSS Optimization

-63%

Potential reduce by 1.9 kB

  • Original 3.0 kB
  • After minification 3.0 kB
  • After compression 1.1 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. Lizzyrob.wedding needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (76%)

Requests Now

17

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lizzyrob.wedding

lizzyrob.wedding

102 ms

www.lizzyrob.wedding

www.lizzyrob.wedding

471 ms

consented-segment.js

consented-segment.js

62 ms

30498a168aaec04a.css

30498a168aaec04a.css

97 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

131 ms

webpack-85a808646c909abe.js

webpack-85a808646c909abe.js

195 ms

framework-a87821de553db91d.js

framework-a87821de553db91d.js

193 ms

main-7164f7df19381639.js

main-7164f7df19381639.js

215 ms

_app-1777bbb32280bd95.js

_app-1777bbb32280bd95.js

193 ms

567-32d6ed001b6aff28.js

567-32d6ed001b6aff28.js

193 ms

546-2fc3ce6d8f43b9d0.js

546-2fc3ce6d8f43b9d0.js

193 ms

%5B%5B...route%5D%5D-6ec0ded7a95ca6b5.js

%5B%5B...route%5D%5D-6ec0ded7a95ca6b5.js

208 ms

_buildManifest.js

_buildManifest.js

206 ms

_ssgManifest.js

_ssgManifest.js

319 ms

_middlewareManifest.js

_middlewareManifest.js

205 ms

css2

css2

78 ms

bf658343-b8b9-4610-9498-c6b39e46e67d~rt_auto-rs_768.h

bf658343-b8b9-4610-9498-c6b39e46e67d~rt_auto-rs_768.h

73 ms

c3f6ff67-752a-458e-9d85-da21d53a6db3~rt_auto-rs_768.h

c3f6ff67-752a-458e-9d85-da21d53a6db3~rt_auto-rs_768.h

69 ms

analytics.min.js

analytics.min.js

41 ms

55edb2b3-3b26-462d-9025-ce1b173a8848~rt_auto-cr_253.214.3183.1680-rs_768.h

55edb2b3-3b26-462d-9025-ce1b173a8848~rt_auto-cr_253.214.3183.1680-rs_768.h

1555 ms

v6-IGZDIOVXH9xtmTZfRagunqBw5WC62cK4.ttf

v6-IGZDIOVXH9xtmTZfRagunqBw5WC62cK4.ttf

67 ms

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFhFTQ7Q.ttf

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFhFTQ7Q.ttf

120 ms

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFiNTQ7Q.ttf

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFiNTQ7Q.ttf

137 ms

nr-spa-1167.min.js

nr-spa-1167.min.js

34 ms

Accessibility Review

lizzyrob.wedding accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

lizzyrob.wedding 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

lizzyrob.wedding SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lizzyrob.wedding 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Lizzyrob.wedding 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

lizzyrob.wedding

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