1.7 sec in total
169 ms
1.4 sec
146 ms
Click here to check amazing Carlos Haynes content. Otherwise, check out these important facts you probably never knew about carloshaynes.com
Visit carloshaynes.comWe analyzed Carloshaynes.com page load time and found that the first response time was 169 ms and then it took 1.5 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.
carloshaynes.com performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value6.7 s
7/100
25%
Value6.0 s
47/100
10%
Value7,010 ms
0/100
30%
Value0
100/100
15%
Value17.7 s
4/100
10%
169 ms
71 ms
82 ms
42 ms
45 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Carloshaynes.com, 56% (29 requests) were made to Static.parastorage.com and 17% (9 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (457 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.0 MB (70%)
2.8 MB
838.5 kB
In fact, the total size of Carloshaynes.com main page is 2.8 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. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 52.1 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 52.1 kB or 82% of the original size.
Potential reduce by 7.9 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. Carlos Haynes images are well optimized though.
Potential reduce by 1.9 MB
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 1.9 MB or 76% of the original size.
Potential reduce by 44.1 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. Carloshaynes.com needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.
Number of requests can be reduced by 37 (77%)
48
11
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carlos Haynes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
carloshaynes.com
169 ms
www.carloshaynes.com
71 ms
bt
82 ms
require.min.js
42 ms
main-r.min.js
45 ms
viewer.css
40 ms
dynamicmodel
8 ms
314137_526d0a803a30077d1a34493d9a49771e_498.json.z
386 ms
314137_5a00073b8ee7caaf8a67cc4081586a49_498.json.z
405 ms
ugc-viewer
82 ms
bt
82 ms
skins.min.js
89 ms
components.min.js
49 ms
utils.min.js
20 ms
core.min.js
172 ms
react-with-addons.min.js
160 ms
lodash.min.js
159 ms
TweenMax.min.js
162 ms
layout.min.js
159 ms
tpa.min.js
170 ms
fonts.min.js
157 ms
animations.min.js
159 ms
swfobject.min.js
157 ms
mousetrap.min.js
161 ms
tweenEngine.min.js
159 ms
DrawSVGPlugin.min.js
160 ms
react-dom.min.js
159 ms
ScrollToPlugin.min.js
165 ms
widgets.min.js
164 ms
experiment.js
159 ms
render.min.js
159 ms
wixappsCore.min.js
160 ms
wixappsBuilder.min.js
158 ms
zepto.min.js
160 ms
color.min.js
160 ms
react-dom-server.min.js
101 ms
bt
293 ms
bt
186 ms
css
78 ms
latin.css
77 ms
b1cd13f9d4dfb1450bbb325285106177.png
26 ms
01113281ebb7dfb57a8dc2a02eb1cb92.png
25 ms
d19374351d7327bf3e6672f901bc3363.png
33 ms
314137_3a52271be6202fcf6ebfecda8510c051.png
457 ms
bt
59 ms
bt
60 ms
bt
60 ms
dc.js
30 ms
5t8vP9Hx2udzw372glmOxA.ttf
35 ms
__utm.gif
15 ms
ga-audiences
51 ms
ugc-viewer
36 ms
carloshaynes.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
Image elements do not have [alt] attributes
carloshaynes.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
carloshaynes.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carloshaynes.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Carloshaynes.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.
carloshaynes.com
Open Graph description is not detected on the main page of Carlos Haynes. 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: