33.5 sec in total
49 ms
2.1 sec
31.3 sec
Welcome to andyyoung.com homepage info - get ready to check Andyyoung best content right away, or after learning these important things about andyyoung.com
Welcome to andyyoung.com. Browse a few of my stories, take a look at my recent projects and read about some of the places I've been.
Visit andyyoung.comWe analyzed Andyyoung.com page load time and found that the first response time was 49 ms and then it took 33.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
andyyoung.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.8 s
3/100
25%
Value7.0 s
32/100
10%
Value1,350 ms
17/100
30%
Value0.012
100/100
15%
Value11.2 s
20/100
10%
49 ms
34 ms
39 ms
95 ms
42 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 49% of them (51 requests) were addressed to the original Andyyoung.com, 25% (26 requests) were made to I0.wp.com and 19% (20 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source I0.wp.com.
Page size can be reduced by 200.4 kB (1%)
22.5 MB
22.3 MB
In fact, the total size of Andyyoung.com main page is 22.5 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. 75% 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 21.8 MB which makes up the majority of the site volume.
Potential reduce by 198.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 198.9 kB or 85% of the original size.
Potential reduce by 0 B
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. Andyyoung images are well optimized though.
Potential reduce by 569 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 1.0 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. Andyyoung.com has all CSS files already compressed.
Number of requests can be reduced by 55 (66%)
83
28
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Andyyoung. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
www.andyyoung.com
49 ms
swiper.min.css
34 ms
style.css
39 ms
style.min.css
95 ms
buttons.min.css
42 ms
dashicons.min.css
49 ms
mediaelementplayer-legacy.min.css
33 ms
wp-mediaelement.min.css
91 ms
media-views.min.css
46 ms
style.min.css
56 ms
style.min.css
65 ms
style.min.css
69 ms
style.min.css
60 ms
style.min.css
74 ms
style.css
71 ms
font-awesome.min.css
87 ms
facebook-login.css
85 ms
elementor-icons.min.css
81 ms
frontend.min.css
97 ms
swiper.min.css
94 ms
post-758.css
105 ms
frontend.min.css
116 ms
global.css
105 ms
post-725.css
113 ms
post-580.css
103 ms
style.min.css
127 ms
css
49 ms
jetpack.css
128 ms
jquery.min.js
127 ms
jquery-migrate.min.js
216 ms
facebook-login.js
152 ms
js
83 ms
imagesloaded.min.js
145 ms
masonry.min.js
144 ms
style.min.js
146 ms
image-cdn.js
145 ms
swiper.min.js
157 ms
facebook-embed.min.js
150 ms
e-202410.js
30 ms
085362df05.js
65 ms
jquery.smartmenus.min.js
158 ms
jetpack-carousel.min.js
324 ms
webpack-pro.runtime.min.js
147 ms
webpack.runtime.min.js
140 ms
frontend-modules.min.js
146 ms
wp-polyfill-inert.min.js
140 ms
regenerator-runtime.min.js
146 ms
wp-polyfill.min.js
142 ms
hooks.min.js
151 ms
i18n.min.js
138 ms
frontend.min.js
149 ms
waypoints.min.js
279 ms
core.min.js
278 ms
frontend.min.js
270 ms
elements-handlers.min.js
267 ms
gtm.js
200 ms
IMG_6642.jpg
399 ms
IMG_5258-scaled.jpg
303 ms
IMG_5258-scaled.jpg
363 ms
IMG_6710-e1534800859195.jpg
496 ms
IMG_6643.jpg
472 ms
IMG_6599.jpg
765 ms
IMG_5784-e1519581540960.jpg
427 ms
IMG_5241.jpg
736 ms
IMG_4924.jpg
731 ms
IMG_4359.jpg
730 ms
IMG_4265.jpg
1073 ms
Lumint-ad-Side-Bar.png
927 ms
Flex-Ad-Side-Bar.png
1076 ms
IMG_6593.jpg
1030 ms
IMG_4230-e1515659971190.jpg
749 ms
IMG_4114.jpg
1384 ms
IMG_4078.jpg
1354 ms
IMG_0088.jpg
931 ms
apple2-bw.jpg
968 ms
dreamstime_m_18320388.jpg
1226 ms
Capture.jpg
1043 ms
img_3729-e1510415290988.jpg
1101 ms
Ad-Time-For-Vacation.png
1817 ms
earth.jpg
1103 ms
Iowa_City.jpg
1406 ms
Video-Image.png
1786 ms
sdk.js
103 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
69 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
105 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
122 ms
KFOkCnqEu92Fr1MmgVxIIzQXKMny.woff
123 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
122 ms
KFOlCnqEu92Fr1MmYUtfBBc-AMP6lQ.woff
124 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0UzdYPFkaVN.woff
124 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0UzdYPFkaVN.woff
123 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0UzdYPFkaVN.woff
125 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0UzdYPFkaVN.woff
124 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0UzdYPFkaVN.woff
125 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0UzdYPFkaVN.woff
169 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0UzdYPFkaVN.woff
169 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8tdE3U3f4TnlY1PG68.woff
127 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8tvE3U3f4TnlY1PG68.woff
125 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8sDE3U3f4TnlY1PG68.woff
125 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8uDFHU3f4TnlY1PG68.woff
169 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8u6FHU3f4TnlY1PG68.woff
126 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8vdFHU3f4TnlY1PG68.woff
126 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8v0FHU3f4TnlY1PG68.woff
169 ms
sdk.js
5 ms
andyyoung.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
andyyoung.com 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
andyyoung.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 Andyyoung.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 Andyyoung.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.
andyyoung.com
Open Graph data is detected on the main page of Andyyoung. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: