Tools & Wizards About Us
sayi.do screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

sayi.do

Custom Wedding Website & Digital RSVP Manager | Say I do

Page Load Speed

1.8 sec in total

First Response

25 ms

Resources Loaded

1 sec

Page Rendered

766 ms

sayi.do screenshot

About Website

Click here to check amazing Say I content for United Kingdom. Otherwise, check out these important facts you probably never knew about sayi.do

Beautiful, customisable wedding websites & the simplest online RSVP, guest list management, checklist and wedding planning tools.

Visit sayi.do

Key Findings

We analyzed Sayi.do page load time and found that the first response time was 25 ms and then it took 1.8 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

sayi.do performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.85

4/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

sayi.do

25 ms

bat.js

63 ms

fbevents.js

36 ms

optimize.js

67 ms

tapfiliate.js

60 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 75% of them (43 requests) were addressed to the original Sayi.do, 4% (2 requests) were made to Bat.bing.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (497 ms) relates to the external source Firebasestorage.googleapis.com.

Page Optimization Overview & Recommendations

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

Content Size

1.8 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Sayi.do main page is 1.8 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 40.5 kB

  • Original 56.8 kB
  • After minification 56.7 kB
  • After compression 16.3 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 40.5 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 6.4 kB

  • Original 1.7 MB
  • After minification 1.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. Say I images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 28 B

  • Original 21.1 kB
  • After minification 21.1 kB
  • After compression 21.1 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.

Requests Breakdown

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

Requests Now

54

After Optimization

29

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

sayi.do

sayi.do

25 ms

bat.js

bat.js

63 ms

fbevents.js

fbevents.js

36 ms

optimize.js

optimize.js

67 ms

tapfiliate.js

tapfiliate.js

60 ms

100367.js

100367.js

61 ms

polyfill-5ae27e69c67d6f4babfd.js

polyfill-5ae27e69c67d6f4babfd.js

8 ms

component---src-pages-index-js-cec982c498ba5e47f119.js

component---src-pages-index-js-cec982c498ba5e47f119.js

25 ms

2894b47e808b69a04f445e460eb2c31531ef5c6b-c7da476a3919f89108a9.js

2894b47e808b69a04f445e460eb2c31531ef5c6b-c7da476a3919f89108a9.js

25 ms

d1b118c378a2e2bf3ac3ab90a8441c7a9fb5934c-9173af8e9c40046c6ce0.js

d1b118c378a2e2bf3ac3ab90a8441c7a9fb5934c-9173af8e9c40046c6ce0.js

25 ms

d49a7b9dd81ec9a75a351889835663003ad0ccbc-8d45f3ed8f09956b37c0.js

d49a7b9dd81ec9a75a351889835663003ad0ccbc-8d45f3ed8f09956b37c0.js

28 ms

commons-09d822b97c2366040082.js

commons-09d822b97c2366040082.js

32 ms

c0d53ec4-148db9b9462dc1f5a6bf.js

c0d53ec4-148db9b9462dc1f5a6bf.js

31 ms

24b1a051-ea525abc2ae74e11cf78.js

24b1a051-ea525abc2ae74e11cf78.js

60 ms

framework-4648bc66ff746d3ebd6a.js

framework-4648bc66ff746d3ebd6a.js

58 ms

app-d2df2aff47351451758d.js

app-d2df2aff47351451758d.js

32 ms

webpack-runtime-5340c30f205f618c27ac.js

webpack-runtime-5340c30f205f618c27ac.js

58 ms

home-hero1-756a82e6908aa99582b661fa9a6c347c.jpg

home-hero1-756a82e6908aa99582b661fa9a6c347c.jpg

137 ms

website-preview1-0f94bf7002451c1ec5e5852012fe4f7b.png

website-preview1-0f94bf7002451c1ec5e5852012fe4f7b.png

195 ms

home-bg2-f634b3edb4dc3ea79c2d8925a9f5457d.jpg

home-bg2-f634b3edb4dc3ea79c2d8925a9f5457d.jpg

169 ms

homepage-section3-843fa95bfdab215942c21d23ff7e7edb.svg

homepage-section3-843fa95bfdab215942c21d23ff7e7edb.svg

187 ms

home-bg-898563bb34913bddfc33f6619b75e161.jpg

home-bg-898563bb34913bddfc33f6619b75e161.jpg

231 ms

excited-woman-265b97a4844cd75b6338a06b84a9bcbe.jpg

excited-woman-265b97a4844cd75b6338a06b84a9bcbe.jpg

344 ms

26336290.js

26336290.js

66 ms

sayi.do

sayi.do

58 ms

rsvp-66c05dad1c55abd3ea7e1942808b3206.jpg

rsvp-66c05dad1c55abd3ea7e1942808b3206.jpg

265 ms

avatar1-bb5b09c1ded10dbbd973f273b16073ff.jpg

avatar1-bb5b09c1ded10dbbd973f273b16073ff.jpg

265 ms

avatar2-450104f7356b1588049db237255725f8.jpg

avatar2-450104f7356b1588049db237255725f8.jpg

266 ms

avatar4-39a73962fe92c378204ac96d1967eb04.jpg

avatar4-39a73962fe92c378204ac96d1967eb04.jpg

349 ms

app-data.json

app-data.json

107 ms

page-data.json

page-data.json

109 ms

3128451518.json

3128451518.json

106 ms

3649515864.json

3649515864.json

106 ms

sayi.do

sayi.do

49 ms

page-data.json

page-data.json

106 ms

page-data.json

page-data.json

41 ms

page-data.json

page-data.json

39 ms

page-data.json

page-data.json

105 ms

page-data.json

page-data.json

195 ms

page-data.json

page-data.json

109 ms

sayi.do

sayi.do

67 ms

js

js

114 ms

assets%2Ftestimonial_avatars%2F456790s.png

assets%2Ftestimonial_avatars%2F456790s.png

302 ms

component---src-pages-pricing-js-f8904fceab756b9d2e6b.js

component---src-pages-pricing-js-f8904fceab756b9d2e6b.js

195 ms

component---src-pages-features-js-3db0a030184e3ef382e4.js

component---src-pages-features-js-3db0a030184e3ef382e4.js

194 ms

av04-77d67e046b268c47032fc81966271c9f.jpg

av04-77d67e046b268c47032fc81966271c9f.jpg

283 ms

av05-47f5bf5bc2cdee4306c8f102a56ae15f.jpg

av05-47f5bf5bc2cdee4306c8f102a56ae15f.jpg

193 ms

assets%2Ftestimonial_avatars%2F29186907_10215131080691694_5830607173075337216_n.jpg

assets%2Ftestimonial_avatars%2F29186907_10215131080691694_5830607173075337216_n.jpg

497 ms

sayidoprimary-medium.woff

sayidoprimary-medium.woff

16 ms

sayidoprimary-regular.woff

sayidoprimary-regular.woff

32 ms

component---src-pages-wedding-website-designs-js-ef6e40986ab9dffa164c.js

component---src-pages-wedding-website-designs-js-ef6e40986ab9dffa164c.js

161 ms

component---src-pages-faq-js-6943a50aa38ef5458b63.js

component---src-pages-faq-js-6943a50aa38ef5458b63.js

171 ms

component---src-pages-wedding-planning-app-features-checklist-js-9cac53bb1d5c478038ca.js

component---src-pages-wedding-planning-app-features-checklist-js-9cac53bb1d5c478038ca.js

250 ms

js

js

38 ms

component---src-pages-find-js-a5c43f52db930c6a028a.js

component---src-pages-find-js-a5c43f52db930c6a028a.js

120 ms

39 ms

28 ms

Accessibility Review

sayi.do accessibility score

73

Accessibility Issues

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

Image elements do not have [alt] attributes

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

sayi.do 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

SEO Factors

sayi.do 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

    EN

  • Encoding

    UTF-8

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

sayi.do

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