Tools & Wizards About Us
weddingeye.com.au screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

weddingeye.com.au

Account Suspended

Page Load Speed

13.4 sec in total

First Response

839 ms

Resources Loaded

11.8 sec

Page Rendered

790 ms

weddingeye.com.au screenshot

About Website

Welcome to weddingeye.com.au homepage info - get ready to check Weddingeye best content right away, or after learning these important things about weddingeye.com.au

Palm Cove photography & video. Cairns wedding photographer servicing any location in Australia. Professional wedding photography & Video service for Cairns wedding, weddings Palm Cove and Port Douglas...

Visit weddingeye.com.au

Key Findings

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

Performance Metrics

weddingeye.com.au performance score

0

Network Requests Diagram

weddingeye.com.au

839 ms

www.palmcovephotography.com

5204 ms

jquery.js

569 ms

jquery-migrate.min.js

559 ms

1430780402_script.js

715 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Weddingeye.com.au, 27% (27 requests) were made to Palmcovephotography.com and 8% (8 requests) were made to Dsms0mj1bbhn4.cloudfront.net. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Palmcovephotography.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 900.9 kB (26%)

Content Size

3.4 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weddingeye.com.au main page is 3.4 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. 60% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 254.2 kB

  • Original 282.5 kB
  • After minification 276.1 kB
  • After compression 28.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 254.2 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 7.8 kB

  • Original 2.2 MB
  • After minification 2.2 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. Weddingeye images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 558.3 kB

  • Original 830.2 kB
  • After minification 829.6 kB
  • After compression 271.9 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 558.3 kB or 67% of the original size.

CSS Optimization

-80%

Potential reduce by 80.6 kB

  • Original 100.6 kB
  • After minification 97.9 kB
  • After compression 19.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. Weddingeye.com.au needs all CSS files to be minified and compressed as it can save up to 80.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (65%)

Requests Now

80

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weddingeye.com.au

weddingeye.com.au

839 ms

www.palmcovephotography.com

www.palmcovephotography.com

5204 ms

jquery.js

jquery.js

569 ms

jquery-migrate.min.js

jquery-migrate.min.js

559 ms

1430780402_script.js

1430780402_script.js

715 ms

1430780402_style.css

1430780402_style.css

870 ms

jquery.shareaholic-publishers-sb.min.js

jquery.shareaholic-publishers-sb.min.js

21 ms

jquery.shareaholic-publishers-rd.min.js

jquery.shareaholic-publishers-rd.min.js

16 ms

Google+-Buttons-91-61-.png

Google+-Buttons-91-61-.png

41 ms

136 ms

Twitter-Buttons-70-10-.png

Twitter-Buttons-70-10-.png

39 ms

Youtube-Buttons-37-34-.png

Youtube-Buttons-37-34-.png

47 ms

Facebook-Buttons-59-68-.png

Facebook-Buttons-59-68-.png

47 ms

nodefaultimage.gif

nodefaultimage.gif

309 ms

masthead_frame_1347126257.jpg

masthead_frame_1347126257.jpg

1540 ms

masthead_image1_1324442956.jpg

masthead_image1_1324442956.jpg

1678 ms

rss-icon.png

rss-icon.png

752 ms

storyboard001.jpg

storyboard001.jpg

2462 ms

storyboard0011.jpg

storyboard0011.jpg

2413 ms

storyboard001.jpg

storyboard001.jpg

3090 ms

0011.jpg

0011.jpg

2169 ms

booo001.jpg

booo001.jpg

2096 ms

Palm-Cove-Wedding-Bride-900.jpg

Palm-Cove-Wedding-Bride-900.jpg

2793 ms

0011.jpg

0011.jpg

3480 ms

Love-in-Wedding-Photos.jpg

Love-in-Wedding-Photos.jpg

2813 ms

borderCAC9C9.gif

borderCAC9C9.gif

2521 ms

tab1-left.jpg

tab1-left.jpg

2656 ms

tab1-right.jpg

tab1-right.jpg

2816 ms

comments-closed.gif

comments-closed.gif

2968 ms

comment.png

comment.png

3131 ms

link.gif

link.gif

3254 ms

email.gif

email.gif

3421 ms

ga.js

ga.js

54 ms

jquery.min.js

jquery.min.js

55 ms

shareaholic.js

shareaholic.js

54 ms

ajax-comments.js

ajax-comments.js

3504 ms

all.js

all.js

8 ms

Cardo99s-webfont.woff

Cardo99s-webfont.woff

3647 ms

shareaholic-analytics.js

shareaholic-analytics.js

52 ms

__utm.gif

__utm.gif

37 ms

sprite.png

sprite.png

4584 ms

shrMain.min.js

shrMain.min.js

53 ms

null.json

null.json

26 ms

77 ms

shareaholic_analytics.js

shareaholic_analytics.js

73 ms

xd_arbiter.php

xd_arbiter.php

36 ms

xd_arbiter.php

xd_arbiter.php

43 ms

wp-loader.js

wp-loader.js

51 ms

ga.js

ga.js

48 ms

jquery.min.js

jquery.min.js

46 ms

header-notifications.js

header-notifications.js

148 ms

analytics.js

analytics.js

126 ms

pageview.gif

pageview.gif

31 ms

xdmStore.js

xdmStore.js

39 ms

partners.js

partners.js

136 ms

remote.html

remote.html

13 ms

notifications.css

notifications.css

9 ms

notifications

notifications

24 ms

sholic.js

sholic.js

4 ms

usermatch

usermatch

36 ms

beacon.js

beacon.js

8 ms

cms-sh2c.html

cms-sh2c.html

61 ms

eexelate.js

eexelate.js

7 ms

7 ms

ep

ep

6 ms

ep

ep

10 ms

pixel

pixel

14 ms

usermatch

usermatch

25 ms

pixel

pixel

13 ms

cm

cm

5 ms

casale

casale

102 ms

pixel

pixel

109 ms

ca

ca

119 ms

casale

casale

117 ms

142 ms

usersync.aspx

usersync.aspx

142 ms

i.gif

i.gif

155 ms

blank.html

blank.html

130 ms

ping_match.gif

ping_match.gif

90 ms

62 ms

net.php

net.php

34 ms

2964

2964

39 ms

casale

casale

10 ms

cfcm.ashx

cfcm.ashx

12 ms

crum

crum

58 ms

pixel

pixel

26 ms

rs

rs

17 ms

generic

generic

17 ms

pixelssl.htm

pixelssl.htm

79 ms

crum

crum

36 ms

match-result

match-result

39 ms

xrefid.xgi

xrefid.xgi

10 ms

ddcssl.htm

ddcssl.htm

24 ms

pixel.gif

pixel.gif

29 ms

pixel.gif

pixel.gif

24 ms

crum

crum

11 ms

xrefid.xgi

xrefid.xgi

5 ms

font-awesome.min.css

font-awesome.min.css

4 ms

analytics_frame.html

analytics_frame.html

85 ms

Accessibility Review

weddingeye.com.au accessibility score

68

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

<frame> or <iframe> elements do not have a title

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

weddingeye.com.au best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

weddingeye.com.au SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weddingeye.com.au 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), while the claimed language is English. Our system also found out that Weddingeye.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

weddingeye.com.au

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