2 sec in total
250 ms
1.3 sec
438 ms
Visit wendygu.com now to see the best up-to-date Wendy Gu content and also check out these interesting facts you probably never knew about wendygu.com
Scientific and medical illustration and animation. Award winning biomedical communicator creating visual solutions for complex concepts in Toronto, Canada.
Visit wendygu.comWe analyzed Wendygu.com page load time and found that the first response time was 250 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
wendygu.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value37.0 s
0/100
25%
Value18.8 s
0/100
10%
Value220 ms
88/100
30%
Value0.049
99/100
15%
Value21.2 s
1/100
10%
250 ms
28 ms
246 ms
253 ms
255 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 89% of them (39 requests) were addressed to the original Wendygu.com, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (770 ms) belongs to the original domain Wendygu.com.
Page size can be reduced by 970.0 kB (14%)
6.9 MB
5.9 MB
In fact, the total size of Wendygu.com main page is 6.9 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 6.2 MB which makes up the majority of the site volume.
Potential reduce by 39.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 23.4 kB, which is 55% 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 39.4 kB or 93% of the original size.
Potential reduce by 487.7 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. Wendy Gu images are well optimized though.
Potential reduce by 168.2 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 168.2 kB or 66% of the original size.
Potential reduce by 274.8 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. Wendygu.com needs all CSS files to be minified and compressed as it can save up to 274.8 kB or 87% of the original size.
Number of requests can be reduced by 11 (26%)
43
32
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wendy Gu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
wendygu.com
250 ms
css
28 ms
bootstrap.css
246 ms
ionicons.css
253 ms
cubeportfolio.css
255 ms
owl.carousel.css
127 ms
style.css
211 ms
jquery-1.12.4.min.js
240 ms
superfish.js
139 ms
cubeportfolio.min.js
329 ms
owl.carousel.min.js
306 ms
main.js
265 ms
analytics.js
48 ms
logo.png
65 ms
retinopathy_preview.jpg
281 ms
crc_preview.jpg
284 ms
hero_preview.jpg
770 ms
mrp_preview.JPG
340 ms
cytokine_preview.jpg
336 ms
cel_1_preview.jpg
251 ms
rhinoplasty_preview.jpg
381 ms
child_er_preview.jpg
375 ms
oby_preview.jpg
363 ms
water_preview.png
617 ms
share_preview.jpg
405 ms
vizbi_preview.jpg
454 ms
mbd_preview.jpg
443 ms
glut_preview.jpg
550 ms
demoReel_preview.JPG
473 ms
birdBills_preview.jpg
533 ms
atherosclerosis_preview.JPG
534 ms
spineSurgery_preview.jpg
538 ms
sgs0217_preview.JPG
599 ms
minds_preview.jpg
642 ms
carbon_preview.jpg
644 ms
wine_preview.jpg
618 ms
trigeminal_preview.jpg
666 ms
medlegal_preview.jpg
699 ms
dysgerminoma_preview.JPG
685 ms
birdCount_preview.jpg
737 ms
skull_preview.jpg
709 ms
collect
12 ms
collect
26 ms
js
79 ms
wendygu.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.
wendygu.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
wendygu.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 Wendygu.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 Wendygu.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.
wendygu.com
Open Graph description is not detected on the main page of Wendy Gu. 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: