1.6 sec in total
386 ms
1.1 sec
70 ms
Click here to check amazing Mary Prince content. Otherwise, check out these important facts you probably never knew about maryprince.org
Here are primary sources that confirm Mary Prince's story, other sources about Mary Prince and enslavement, and instructional materials.
Visit maryprince.orgWe analyzed Maryprince.org page load time and found that the first response time was 386 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
maryprince.org performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value6.7 s
7/100
25%
Value2.0 s
100/100
10%
Value400 ms
67/100
30%
Value0.004
100/100
15%
Value9.0 s
33/100
10%
386 ms
39 ms
38 ms
31 ms
261 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Maryprince.org, 35% (14 requests) were made to Static.parastorage.com and 30% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (572 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 279.3 kB (37%)
762.2 kB
482.8 kB
In fact, the total size of Maryprince.org main page is 762.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 321.5 kB which makes up the majority of the site volume.
Potential reduce by 232.5 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 232.5 kB or 72% of the original size.
Potential reduce by 44.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. Obviously, Mary Prince needs image optimization as it can save up to 44.1 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.7 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.
Number of requests can be reduced by 10 (40%)
25
15
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mary Prince. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.maryprince.org
386 ms
minified.js
39 ms
focus-within-polyfill.js
38 ms
polyfill.min.js
31 ms
957ac1_415931a862264dbc8ad12494fefef0bb.jpg
261 ms
bundle.min.js
56 ms
thunderbolt-commons.24e46262.bundle.min.js
26 ms
main.8752ee81.bundle.min.js
32 ms
lodash.min.js
35 ms
react.production.min.js
93 ms
react-dom.production.min.js
92 ms
siteTags.bundle.min.js
79 ms
wix-perf-measure.umd.min.js
78 ms
957ac1_88d6cbaba556480da58ea6210cab803d.jpg
295 ms
957ac1_4e2edbf03f7b4ae8b296bfefb7138117.jpg
253 ms
957ac1_4404c5cb8a3b485da21d7725734005da.png
266 ms
957ac1_b1aaf6640c36412da6c02a40412224b7.png
310 ms
957ac1_5dc8e56c7f3149a6bad5dfe38134dcd3.png
291 ms
957ac1_343528f9bf784327ab18d24ffe1cac4f.png
446 ms
957ac1_3b7ab0ac890e4bd6b92c8dc3adfe35da~mv2_d_1575_2400_s_2.jpg
572 ms
84770f_6bbe4230fd71efea7703ecffee091215.png
268 ms
84770f_9c23f56a09a7f06d4dbf80ed6fdcd2e4.png
289 ms
171 ms
172 ms
179 ms
169 ms
177 ms
172 ms
204 ms
203 ms
210 ms
211 ms
206 ms
193 ms
opensans-regular-webfont.woff
14 ms
opensans-bold-webfont.woff
8 ms
deprecation-en.v5.html
8 ms
bolt-performance
29 ms
deprecation-style.v5.css
11 ms
right-arrow.svg
12 ms
maryprince.org accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
maryprince.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
maryprince.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maryprince.org 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 Maryprince.org 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.
maryprince.org
Open Graph data is detected on the main page of Mary Prince. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: