4.5 sec in total
212 ms
3.8 sec
534 ms
Click here to check amazing Marry Me Mary content. Otherwise, check out these important facts you probably never knew about marrymemary.com.au
An experienced Sydney based Marriage Celebrant creating cherished memories of love, happiness and joy. Call her on 0400 363 563 today.
Visit marrymemary.com.auWe analyzed Marrymemary.com.au page load time and found that the first response time was 212 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
marrymemary.com.au performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value16.4 s
0/100
25%
Value15.6 s
0/100
10%
Value1,700 ms
11/100
30%
Value0.009
100/100
15%
Value16.7 s
5/100
10%
212 ms
2067 ms
27 ms
75 ms
46 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 69% of them (65 requests) were addressed to the original Marrymemary.com.au, 14% (13 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Marrymemary.com.au.
Page size can be reduced by 2.5 MB (62%)
4.1 MB
1.5 MB
In fact, the total size of Marrymemary.com.au main page is 4.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.6 MB which makes up the majority of the site volume.
Potential reduce by 50.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 50.7 kB or 84% of the original size.
Potential reduce by 16.6 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. Marry Me Mary images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 70% of the original size.
Potential reduce by 1.3 MB
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. Marrymemary.com.au needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 89% of the original size.
Number of requests can be reduced by 53 (69%)
77
24
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Marry Me Mary. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
marrymemary.com.au
212 ms
www.marrymemary.com.au
2067 ms
css
27 ms
layerslider.css
75 ms
css
46 ms
styles.css
147 ms
frontend.css
149 ms
style.css
148 ms
font-awesome.min.css
151 ms
style.min.css
156 ms
stylesheet.min.css
304 ms
webkit_stylesheet.css
216 ms
style_dynamic.css
220 ms
responsive.min.css
225 ms
style_dynamic_responsive.css
221 ms
js_composer.min.css
398 ms
custom_css.css
288 ms
greensock.js
367 ms
jquery.js
366 ms
jquery-migrate.min.js
291 ms
layerslider.kreaturamedia.jquery.js
480 ms
layerslider.transitions.js
364 ms
jquery.fitvids.min.js
375 ms
frontend.min.js
505 ms
js
38 ms
formreset.min.css
534 ms
formsmain.min.css
535 ms
readyclass.min.css
543 ms
browsers.min.css
545 ms
datepicker.min.css
576 ms
jquery.json-1.3.js
581 ms
gravityforms.min.js
583 ms
core.min.js
583 ms
datepicker.min.js
584 ms
datepicker.min.js
584 ms
jquery.form.min.js
632 ms
scripts.js
632 ms
qode-like.min.js
631 ms
plugins.js
1009 ms
jquery.carouFredSel-6.2.1.min.js
632 ms
lemmon-slider.min.js
633 ms
jquery.fullPage.min.js
621 ms
jquery.mousewheel.min.js
546 ms
jquery.touchSwipe.min.js
544 ms
isotope.pkgd.min.js
577 ms
default_dynamic.js
570 ms
default.min.js
711 ms
custom_js.js
543 ms
comment-reply.min.js
567 ms
js_composer_front.min.js
567 ms
wp-embed.min.js
571 ms
wp-emoji-release.min.js
592 ms
ga.js
81 ms
118585177
135 ms
MarryMeMary-Logo-DS3.png
387 ms
MarryMeMary@2x.png
346 ms
MarryMeMaryDark@2x.png
345 ms
logo_white.png
369 ms
MarryMeMary-BG2.jpg
848 ms
ICON-bi-copy-e1458003483852.jpg
424 ms
ICON-ceremony-e1458015900931.jpg
424 ms
ICON-el-copy-e1458003246129.jpg
437 ms
ICON-mu-copy-e1458002549309.jpg
466 ms
ICON-oc-e1458002166312.jpg
675 ms
ICON-oc-copy-e1458003609901.jpg
670 ms
ICON-se-copy-e1458019798799.jpg
669 ms
registry-button1-e1458002005376.jpeg
639 ms
D9A9229-2.jpg
833 ms
gZ8EM_Gzaq4WRjCimioyzQ.woff
45 ms
fontawesome-webfont.woff
789 ms
QHIOz1iKF3bIEzRdDFaf5dCpxY7g_VZuMtgz78Sasn8.woff
46 ms
kH7K4InNTm7mmOXXjrA5v2bXv0mI0yfCBzn-qhU0FPM.woff
46 ms
pR0sBQVcY0JZc_ciXjFsK2vhaIAz1NJzluD_h2UBN7c.woff
46 ms
__utm.gif
29 ms
vQbQAx9WlNOTTgpOnfyPXQ.woff
33 ms
Li18TEFObx_yGdzKDoI_chsxEYwM7FgeyaSgU71cLG0.woff
32 ms
ZKwULyCG95tk6mOqHQfRBBsxEYwM7FgeyaSgU71cLG0.woff
33 ms
cbAbzEjxTdN5KKmS-gA0tRsxEYwM7FgeyaSgU71cLG0.woff
34 ms
rr0ijB5_2nAJsAoZ6vECXT8E0i7KZn-EPnyo3HZu7kw.woff
69 ms
STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff
69 ms
WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff
36 ms
QoPu455RxV2raYSIFXAMBRsxEYwM7FgeyaSgU71cLG0.woff
35 ms
Ji5epXNcpHu3r63lhS0cThsxEYwM7FgeyaSgU71cLG0.woff
37 ms
player.js
137 ms
player.css
129 ms
ga.js
98 ms
vuid.min.js
137 ms
collect
137 ms
__utm.gif
33 ms
ga-audiences
104 ms
proxy.html
51 ms
505655107.webp
140 ms
3681675_60x60.jpg
149 ms
calendar.png
77 ms
marrymemary.com.au accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
marrymemary.com.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
marrymemary.com.au SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Marrymemary.com.au 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 Marrymemary.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.
marrymemary.com.au
Open Graph description is not detected on the main page of Marry Me Mary. 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: