Tools & Wizards About Us
i-do.com.au screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

i-do.com.au

Wedding Dresses, Venues, Invitations, Flowers, Gowns, Cakes

Page Load Speed

5.2 sec in total

First Response

513 ms

Resources Loaded

4.3 sec

Page Rendered

375 ms

i-do.com.au screenshot

About Website

Visit i-do.com.au now to see the best up-to-date I Do content for Australia and also check out these interesting facts you probably never knew about i-do.com.au

Wedding Tips, Articles, Advice, Videos and thousands of local wedding suppliers. i-do.com.au, Everything you need from yes to ... i-do.

Visit i-do.com.au

Key Findings

We analyzed I-do.com.au page load time and found that the first response time was 513 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

i-do.com.au performance score

0

Network Requests Diagram

i-do.com.au

513 ms

staging.i-do.com.au

860 ms

map.css

476 ms

normalise.css

477 ms

base.css

484 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original I-do.com.au, 64% (48 requests) were made to Staging.i-do.com.au and 7% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Staging.i-do.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (47%)

Content Size

3.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I-do.com.au 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. 55% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 136.9 kB

  • Original 181.6 kB
  • After minification 178.5 kB
  • After compression 44.7 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 136.9 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 110.6 kB

  • Original 1.2 MB
  • After minification 1.1 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. I Do images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 997.5 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 419.2 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 997.5 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 191.7 kB

  • Original 232.6 kB
  • After minification 160.6 kB
  • After compression 40.9 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. I-do.com.au needs all CSS files to be minified and compressed as it can save up to 191.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (63%)

Requests Now

60

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

i-do.com.au

i-do.com.au

513 ms

staging.i-do.com.au

staging.i-do.com.au

860 ms

map.css

map.css

476 ms

normalise.css

normalise.css

477 ms

base.css

base.css

484 ms

content.css

content.css

480 ms

masonry-panels.css

masonry-panels.css

481 ms

colour-palette.css

colour-palette.css

484 ms

articles.css

articles.css

713 ms

font-awesome.min.css

font-awesome.min.css

718 ms

forms.css

forms.css

717 ms

tab-style.css

tab-style.css

721 ms

legacy-base-layout.css

legacy-base-layout.css

724 ms

legacy-styles.css

legacy-styles.css

723 ms

widgets.css

widgets.css

953 ms

directory.css

directory.css

956 ms

jquery.min.js

jquery.min.js

31 ms

magnific-popup.css

magnific-popup.css

955 ms

magnific-min.js

magnific-min.js

1198 ms

masonry.css

masonry.css

984 ms

masonry.pkgd.js

masonry.pkgd.js

6 ms

script.js

script.js

985 ms

styles.css

styles.css

1189 ms

ScriptResource.axd

ScriptResource.axd

1199 ms

default.aspx

default.aspx

1015 ms

addthis_widget.js

addthis_widget.js

11 ms

css

css

62 ms

css

css

14 ms

gpt.js

gpt.js

4 ms

pubads_impl_81.js

pubads_impl_81.js

10 ms

container.html

container.html

13 ms

analytics.js

analytics.js

19 ms

i-do-blue_mob.png

i-do-blue_mob.png

271 ms

Twitter.png

Twitter.png

270 ms

Pinterest.png

Pinterest.png

271 ms

Facebook.png

Facebook.png

271 ms

Instagram.png

Instagram.png

271 ms

460_300w.jpg

460_300w.jpg

659 ms

list23.png

list23.png

482 ms

463_300w.jpg

463_300w.jpg

487 ms

box39.png

box39.png

484 ms

188_300w.jpg

188_300w.jpg

480 ms

heart301.png

heart301.png

487 ms

462_300w.jpg

462_300w.jpg

956 ms

light61.png

light61.png

721 ms

3171_600w.jpg

3171_600w.jpg

997 ms

2423_600w.jpg

2423_600w.jpg

1203 ms

3074_600w.jpg

3074_600w.jpg

1439 ms

3123_600w.jpg

3123_600w.jpg

1133 ms

11995_640w.jpg

11995_640w.jpg

1675 ms

9558_640w.jpg

9558_640w.jpg

1195 ms

6242_640w.jpg

6242_640w.jpg

1240 ms

i-do-logo-black.png

i-do-logo-black.png

1372 ms

collect

collect

12 ms

collect

collect

54 ms

chevron-green.png

chevron-green.png

1218 ms

gtm.js

gtm.js

62 ms

get-loader

get-loader

17 ms

i-do-blue_tiny.png

i-do-blue_tiny.png

1177 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

64 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

77 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

93 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

104 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1450 ms

RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf

RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf

114 ms

my-wisepop

my-wisepop

183 ms

1135 ms

49948.js

49948.js

180 ms

477 ms

300lo.json

300lo.json

56 ms

wisepop-close-button2.png

wisepop-close-button2.png

22 ms

08f768115f50ccf4acfc6c397a0875df.png

08f768115f50ccf4acfc6c397a0875df.png

166 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

23 ms

layers.3643cb2e25fb91c29386.js

layers.3643cb2e25fb91c29386.js

12 ms

js

js

22 ms

SEO Factors

i-do.com.au SEO score

0

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 I-do.com.au 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 I-do.com.au 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

i-do.com.au

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