12.1 sec in total
3 sec
8.9 sec
169 ms
Click here to check amazing Mary Mae S content. Otherwise, check out these important facts you probably never knew about marymaes.com.au
Visit marymaes.com.auWe analyzed Marymaes.com.au page load time and found that the first response time was 3 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
marymaes.com.au performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value18.6 s
0/100
25%
Value15.8 s
0/100
10%
Value1,700 ms
11/100
30%
Value0
100/100
15%
Value17.8 s
4/100
10%
3042 ms
65 ms
650 ms
53 ms
84 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 49% of them (27 requests) were addressed to the original Marymaes.com.au, 20% (11 requests) were made to Cdnjs.cloudflare.com and 7% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Marymaes.com.au.
Page size can be reduced by 262.2 kB (3%)
9.2 MB
8.9 MB
In fact, the total size of Marymaes.com.au main page is 9.2 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 8.7 MB which makes up the majority of the site volume.
Potential reduce by 61.9 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 61.9 kB or 82% of the original size.
Potential reduce by 102.1 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. Mary Mae S images are well optimized though.
Potential reduce by 29.0 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.
Potential reduce by 69.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. Marymaes.com.au needs all CSS files to be minified and compressed as it can save up to 69.1 kB or 81% of the original size.
Number of requests can be reduced by 25 (49%)
51
26
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mary Mae S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
marymaes.com.au
3042 ms
gtm.js
65 ms
sbi-styles.min.css
650 ms
js
53 ms
js
84 ms
js
82 ms
analytics.js
21 ms
collect
38 ms
collect
111 ms
css2
51 ms
bootstrap.min.css
37 ms
style.min.css
610 ms
bootstrap-icons.min.css
163 ms
gijgo.min.css
45 ms
swiper-bundle.css
48 ms
SmoothScroll.min.js
49 ms
swiper-bundle.min.js
51 ms
ga-audiences
28 ms
jquery.min.js
9 ms
jquery-migrate.min.js
8 ms
gijgo.min.js
11 ms
bootstrap.min.js
12 ms
api.js
26 ms
app.min.js
437 ms
sbi-scripts.min.js
701 ms
288054239_530846085391047_3651855932538368423_n.jpg
903 ms
sbi-sprite.png
220 ms
twg-logo.png
222 ms
pexels-eyl%C3%BCl-10646022-scaled.jpg
2389 ms
MARYMAES_MAINLOGO.png
446 ms
MARYMAES_NAVLOGO.png
664 ms
MaryMaes_VenueRefresh_May22_6.jpg
1556 ms
MaryMaes_VenueRefresh_May22_267.jpg
1741 ms
MaryMaes_VenueRefresh_May22_212.jpg
1525 ms
MaryMaes_VenueRefresh_May22_185.jpg
1333 ms
HOME-1-1.jpeg
1530 ms
MaryMaes_VenueRefresh_May22_176.jpg
1555 ms
Mary_Maes_-108.jpg
2180 ms
S_D_610.jpg
2620 ms
marymaes.com.au
3496 ms
384-Thea-_-Dudley-scaled.jpg
1776 ms
JMP210515-0526-scaled.jpg
2177 ms
placeholder.png
1994 ms
652c9524fba0737a43d1ec86.js
601 ms
bootstrap-icons.woff
152 ms
fbevents.js
23 ms
recaptcha__en.js
52 ms
370523377_683138190506853_8752751188692902723_nlow.jpg
1920 ms
370486218_683133683840637_6259520178729431179_nlow.jpg
2102 ms
370611839_683130460507626_5549969598948472244_nlow.jpg
2105 ms
369800659_679676830852989_2216229077231566460_nlow.jpg
2138 ms
368783273_679668920853780_1517360718634088944_nlow.jpg
2311 ms
intlTelInput.min.js
12 ms
intlTelInputUtils.min.js
32 ms
intlTelInput.min.css
26 ms
marymaes.com.au accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
marymaes.com.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
marymaes.com.au SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Marymaes.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 Marymaes.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.
marymaes.com.au
Open Graph description is not detected on the main page of Mary Mae S. 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: