2.7 sec in total
203 ms
1.3 sec
1.2 sec
Click here to check amazing Mary S content. Otherwise, check out these important facts you probably never knew about marys.com
Shop the newest designer bridal gowns and dresses perfect for prom or special occasion at Mary's Designer Bridal Boutique in Annapolis, Maryland!
Visit marys.comWe analyzed Marys.com page load time and found that the first response time was 203 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
marys.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value23.4 s
0/100
25%
Value24.3 s
0/100
10%
Value40,570 ms
0/100
30%
Value0.133
81/100
15%
Value55.0 s
0/100
10%
203 ms
81 ms
29 ms
80 ms
45 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 76% of them (53 requests) were addressed to the original Marys.com, 14% (10 requests) were made to Use.typekit.net and 3% (2 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (543 ms) relates to the external source Js.driftt.com.
Page size can be reduced by 125.0 kB (3%)
4.2 MB
4.1 MB
In fact, the total size of Marys.com main page is 4.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. 85% 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. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 66.4 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. This page needs HTML code to be minified as it can gain 20.7 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.4 kB or 86% of the original size.
Potential reduce by 58.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. Mary S images are well optimized though.
Potential reduce by 50 B
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 0 B
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.
Number of requests can be reduced by 5 (8%)
59
54
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mary 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 6 to 1 for JavaScripts and as a result speed up the page load time.
www.marys.com
203 ms
mzr3rax.css
81 ms
theme.min.css
29 ms
theme.min.js
80 ms
p.css
45 ms
gtm.js
542 ms
u4ndfke4kb83.js
543 ms
main-logo
467 ms
iframe_api
515 ms
ab366a76_26ff_4dd3_81a4_4014fe581039.jpg
273 ms
13b5513f_d47d_4949_bb91_5da41bcd442d.jpg
382 ms
www.marys.com
380 ms
2e210d16_84fc_4e4a_8ba3_8244e473b8d7.jpg
504 ms
87c9e67e_6a51_4179_9548_97a8f5adc554.jpg
509 ms
6101164d_1447_4fa7_b47d_1f04db8c3aad.jpg
509 ms
d7ff35b0_fee7_4368_8b3e___5d42746a7b.jpg
510 ms
featured-about.jpg
455 ms
featured-about2.jpg
455 ms
featured-about2-mobile.jpg
506 ms
featured-designer1.jpg
507 ms
featured-designer2.jpg
514 ms
featured-designer3.jpg
511 ms
Ardi_front_4__1_.jpg
524 ms
featured-banner-mobile.jpg
518 ms
featured-banner.jpg
516 ms
step2.svg
511 ms
step.svg
514 ms
featured-dress1.jpg
518 ms
featured-dress2.jpg
518 ms
featured-testimonial.jpg
518 ms
featured-testimonial-mobile.jpg
520 ms
quote-left.png
521 ms
quote-right.png
519 ms
featured-collection1.jpg
521 ms
featured-collection2.jpg
522 ms
featured-collection3.jpg
523 ms
18317617945012408.webp
523 ms
17993728507555642.webp
524 ms
17990162245560778.webp
523 ms
18315497116005251.webp
524 ms
18260846752099690.webp
524 ms
17971369237828430.webp
524 ms
17845048700845510.webp
526 ms
17959463620991685.webp
527 ms
d
261 ms
d
353 ms
d
262 ms
d
220 ms
d
201 ms
d
219 ms
d
293 ms
d
221 ms
d
293 ms
analytics.js
270 ms
icomoon.ttf
258 ms
17996515648480547.webp
187 ms
17850835001834151.webp
152 ms
17977010140727842.webp
81 ms
17974261255783861.webp
78 ms
17956846379046188.webp
104 ms
17986328131584627.webp
101 ms
18225467326156941.webp
100 ms
17881710914727233.webp
99 ms
17920245602594436.webp
102 ms
17953477769115919.webp
99 ms
18018718060430027.webp
101 ms
17923550810533598.webp
97 ms
subscribe-logo.png
96 ms
www-widgetapi.js
43 ms
collect
30 ms
marys.com 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
[aria-hidden="true"] elements contain focusable descendents
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
marys.com 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
marys.com SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Marys.com 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 Marys.com 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.
marys.com
Open Graph data is detected on the main page of Mary S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: