12.5 sec in total
1.7 sec
10.6 sec
122 ms
Click here to check amazing Carl W Gray content. Otherwise, check out these important facts you probably never knew about carlwgray.com
Carl Wayne Gray Genealogies
Visit carlwgray.comWe analyzed Carlwgray.com page load time and found that the first response time was 1.7 sec and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
carlwgray.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value8.8 s
1/100
25%
Value7.6 s
25/100
10%
Value1,100 ms
23/100
30%
Value0.037
100/100
15%
Value11.8 s
17/100
10%
1740 ms
7156 ms
78 ms
112 ms
238 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 73% of them (61 requests) were addressed to the original Carlwgray.com, 8% (7 requests) were made to Translate.googleapis.com and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (7.2 sec) relates to the external source Claycity.carlwgray.com.
Page size can be reduced by 471.3 kB (49%)
965.2 kB
494.0 kB
In fact, the total size of Carlwgray.com main page is 965.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. 50% of websites need less resources to load. Javascripts take 440.7 kB which makes up the majority of the site volume.
Potential reduce by 57.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 57.9 kB or 80% of the original size.
Potential reduce by 9.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. Carl W Gray images are well optimized though.
Potential reduce by 249.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 249.5 kB or 57% of the original size.
Potential reduce by 154.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. Carlwgray.com needs all CSS files to be minified and compressed as it can save up to 154.8 kB or 68% of the original size.
Number of requests can be reduced by 48 (65%)
74
26
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carl W Gray. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
carlwgray.com
1740 ms
claycity.carlwgray.com
7156 ms
css
78 ms
style.css
112 ms
dashicons.min.css
238 ms
desktop_style.css
148 ms
styles.css
165 ms
sbtt-front.css
197 ms
weaverx-ts-style.min.css
149 ms
styles.css
207 ms
atw-posts-style.min.css
222 ms
color-picker.min.css
287 ms
colorbox.css
301 ms
style.css
309 ms
style.css
337 ms
fonts.min.css
388 ms
style-weaverx.min.css
340 ms
wppa-style.css
363 ms
jquery.js
514 ms
jquery-migrate.min.js
396 ms
jquery.form.min.js
412 ms
wppa-utils.min.js
421 ms
wppa.min.js
432 ms
wppa-slideshow.min.js
458 ms
wppa-ajax-front.min.js
472 ms
wppa-popup.min.js
490 ms
wppa-init.en.js
495 ms
front_end_script.js
534 ms
sbtt.js
535 ms
jquery.colorbox-min.js
549 ms
core.min.js
576 ms
widget.min.js
1053 ms
mouse.min.js
1069 ms
draggable.min.js
1054 ms
slider.min.js
1048 ms
jquery.ui.touch-punch.js
1051 ms
iris.min.js
1050 ms
js
76 ms
googlemap.js
1173 ms
main.js
1172 ms
element.js
73 ms
main.js
1062 ms
weaverxjslib.min.js
1029 ms
scripts.js
1016 ms
customize.js
1058 ms
weaverxjslib-end.min.js
1054 ms
wp-embed.min.js
1043 ms
wp-emoji-release.min.js
1028 ms
gr.png
243 ms
search-black.png
234 ms
maroon-bells.jpg
235 ms
coffee-2.gif
233 ms
148.jpg
344 ms
01n.png
232 ms
02d.png
233 ms
10d.png
233 ms
fulls.png
234 ms
loading.gif
235 ms
all.png
329 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
43 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
51 ms
xjAJXh38I15wypJXxuGMBtIh4imgI8P11RFo6YPCPC0.woff
63 ms
PRmiXeptR36kaC0GEAetxoUt79146ZFaIJxILcpzmhI.woff
60 ms
translateelement.css
66 ms
main.js
216 ms
backtotop.png
118 ms
wcp-ow-icon.woff
135 ms
roboto-regular.woff
286 ms
roboto-regular.woff
293 ms
roboto-bold.woff
333 ms
roboto-bold.woff
310 ms
dosis-bold.woff
266 ms
Genericons.svg
309 ms
8AAnjaY2BgYGQAgjO2i86D6AshzNIwGgBAmQUAAAA=
2 ms
element_main.js
37 ms
translate_24dp.png
31 ms
l
43 ms
googlelogo_color_42x16dp.png
23 ms
googlelogo_color_68x28dp.png
5 ms
cleardot.gif
33 ms
te_ctrl3.gif
20 ms
loading.gif
20 ms
te_bk.gif
11 ms
carlwgray.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
Buttons do not have an accessible name
Links do not have a discernible 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.
carlwgray.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
carlwgray.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Carlwgray.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 Carlwgray.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.
carlwgray.com
Open Graph description is not detected on the main page of Carl W Gray. 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: