6.8 sec in total
831 ms
1.8 sec
4.1 sec
Click here to check amazing Sandra Says content. Otherwise, check out these important facts you probably never knew about sandrasays.com
…what Sandra says about technology, communications, friends and other things…
Visit sandrasays.comWe analyzed Sandrasays.com page load time and found that the first response time was 831 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sandrasays.com performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value5.7 s
16/100
25%
Value2.0 s
99/100
10%
Value60 ms
100/100
30%
Value0.001
100/100
15%
Value4.5 s
82/100
10%
831 ms
28 ms
42 ms
12 ms
25 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 36% of them (27 requests) were addressed to the original Sandrasays.com, 13% (10 requests) were made to Pixel.wp.com and 9% (7 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (831 ms) belongs to the original domain Sandrasays.com.
Page size can be reduced by 866.8 kB (26%)
3.4 MB
2.5 MB
In fact, the total size of Sandrasays.com 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. 80% 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 33.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 33.5 kB or 77% of the original size.
Potential reduce by 7.4 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. Sandra Says images are well optimized though.
Potential reduce by 505.5 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 505.5 kB or 67% of the original size.
Potential reduce by 320.4 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. Sandrasays.com needs all CSS files to be minified and compressed as it can save up to 320.4 kB or 75% of the original size.
Number of requests can be reduced by 50 (76%)
66
16
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sandra Says. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
sandrasays.com
831 ms
wp-emoji-release.min.js
28 ms
style.css
42 ms
dashicons.min.css
12 ms
css
25 ms
style.css
91 ms
genericons.css
21 ms
jetpack.css
11 ms
jquery.js
52 ms
jquery-migrate.min.js
30 ms
responsive-menu.js
45 ms
sticky-message.js
31 ms
devicepx-jetpack.js
16 ms
gprofiles.js
63 ms
wpgroho.js
78 ms
wp-embed.min.js
60 ms
postmessage.js
64 ms
jquery.jetpack-resize.js
68 ms
jquery.inview.js
73 ms
queuehandler.js
70 ms
sharing.js
197 ms
e-201611.js
13 ms
analytics.js
294 ms
bg.png
309 ms
cropped-SSnewLogo-SQ.jpg
307 ms
logo-drive.png
213 ms
BDP8ZAPF2Z.jpg
320 ms
hispanics_1456606215.jpg
315 ms
rss.png
316 ms
loading.gif
211 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
295 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
298 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
296 ms
LqowQDslGv4DmUBAfWa2Vw.ttf
299 ms
Genericons.svg
304 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
209 ms
ssi-icomoon.woff
312 ms
master.html
296 ms
hovercard.css
154 ms
services.css
191 ms
share
270 ms
g.gif
171 ms
count.json
185 ms
graph.facebook.com
183 ms
share
271 ms
count.json
172 ms
graph.facebook.com
167 ms
share
257 ms
count.json
162 ms
graph.facebook.com
162 ms
g.gif
143 ms
g.gif
208 ms
g.gif
208 ms
g.gif
237 ms
g.gif
237 ms
g.gif
236 ms
g.gif
238 ms
g.gif
238 ms
v0rPu_pl0D8
287 ms
collect
164 ms
g.gif
149 ms
jquery.js
111 ms
collect
66 ms
postmessage.js
6 ms
jed.js
6 ms
underscore.min.js
6 ms
www-embed-player-vflfNyN_r.css
38 ms
www-embed-player.js
77 ms
jquery.wpcom-proxy-request.js
8 ms
160 ms
likes-rest.js
92 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
91 ms
ad_status.js
86 ms
103 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
122 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
123 ms
sandrasays.com 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
sandrasays.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
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
sandrasays.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sandrasays.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 Sandrasays.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.
sandrasays.com
Open Graph data is detected on the main page of Sandra Says. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: