3.4 sec in total
271 ms
2.3 sec
825 ms
Visit randcosmeticsurgery.com now to see the best up-to-date Rand Cosmetic Surgery content and also check out these interesting facts you probably never knew about randcosmeticsurgery.com
Dr. Rand is a board-certified plastic surgeon serving Bellevue and Seattle with breast augmentation, liposuction, facelift and many other cosmetic procedures.
Visit randcosmeticsurgery.comWe analyzed Randcosmeticsurgery.com page load time and found that the first response time was 271 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
randcosmeticsurgery.com performance score
name
value
score
weighting
Value3.7 s
28/100
10%
Value8.8 s
1/100
25%
Value6.6 s
37/100
10%
Value1,200 ms
21/100
30%
Value0
100/100
15%
Value12.1 s
16/100
10%
271 ms
469 ms
71 ms
20 ms
141 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 50% of them (28 requests) were addressed to the original Randcosmeticsurgery.com, 13% (7 requests) were made to Fast.fonts.net and 9% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Randcosmeticsurgery.com.
Page size can be reduced by 411.7 kB (36%)
1.1 MB
718.4 kB
In fact, the total size of Randcosmeticsurgery.com main page is 1.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. 65% of websites need less resources to load. HTML takes 467.9 kB which makes up the majority of the site volume.
Potential reduce by 400.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 400.9 kB or 86% of the original size.
Potential reduce by 6.5 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. Rand Cosmetic Surgery images are well optimized though.
Potential reduce by 4.3 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 15 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. Randcosmeticsurgery.com has all CSS files already compressed.
Number of requests can be reduced by 22 (48%)
46
24
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rand Cosmetic Surgery. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
randcosmeticsurgery.com
271 ms
www.randcosmeticsurgery.com
469 ms
34e7172d-0832-4e3f-aecb-5978a7e8613a.js
71 ms
mt.js
20 ms
js
141 ms
69810.js
121 ms
34e7172d-0832-4e3f-aecb-5978a7e8613a.js
54 ms
js
191 ms
jquery.js
98 ms
wow.js
452 ms
modernizr.js
117 ms
jquery.cycle2.min.js
117 ms
custom.js
452 ms
gallery-default.js
451 ms
equalheights.js
116 ms
owl.carousel.min.js
473 ms
jquery.magnific-popup.min.js
451 ms
api.js
168 ms
recaptcha.js
160 ms
foundation.min.js
234 ms
foundation.abide.min.js
398 ms
logo.png
474 ms
logo2x.png
662 ms
icons.svg
470 ms
slider.jpg
839 ms
realself.png
747 ms
myFace.png
708 ms
castle.png
687 ms
home-bio.png
835 ms
home-bio-left.jpg
963 ms
home-bio.jpg
1176 ms
logo-footer.png
932 ms
logo-footer2x.png
970 ms
star.png
1090 ms
f1f853cb-6239-4c68-b259-70b41671b488.ttf
130 ms
a842cfef-4388-46ae-854c-d7b0cfc07428.ttf
137 ms
14f9135a-8687-4aef-81e4-1a669f3b9152.ttf
301 ms
7869ff0a-c18f-4ce1-bf07-fbf5b7172b66.ttf
303 ms
analytics.js
245 ms
js
79 ms
js
244 ms
244 ms
loader.js
243 ms
collect
44 ms
www.randcosmeticsurgery.com
816 ms
20 ms
call-tracking_7.js
6 ms
wcm
13 ms
app.js
103 ms
recaptcha__en.js
24 ms
fallback
26 ms
fallback__ltr.css
5 ms
css
27 ms
logo_48.png
5 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
17 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
23 ms
randcosmeticsurgery.com 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
Links do not have a discernible name
randcosmeticsurgery.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
randcosmeticsurgery.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 Randcosmeticsurgery.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 Randcosmeticsurgery.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.
randcosmeticsurgery.com
Open Graph data is detected on the main page of Rand Cosmetic Surgery. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: