5 sec in total
859 ms
3.3 sec
791 ms
Welcome to tomgreen.com homepage info - get ready to check Tom Green best content for United States right away, or after learning these important things about tomgreen.com
Webovision
Visit tomgreen.comWe analyzed Tomgreen.com page load time and found that the first response time was 859 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
tomgreen.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value13.9 s
0/100
25%
Value6.8 s
35/100
10%
Value110 ms
98/100
30%
Value0.001
100/100
15%
Value13.2 s
12/100
10%
859 ms
55 ms
65 ms
63 ms
82 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 60% of them (36 requests) were addressed to the original Tomgreen.com, 13% (8 requests) were made to Youtube.com and 5% (3 requests) were made to Gumroad.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Tomgreen.com.
Page size can be reduced by 925.3 kB (40%)
2.3 MB
1.4 MB
In fact, the total size of Tomgreen.com main page is 2.3 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 18.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 3.4 kB, which is 14% 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 18.4 kB or 77% of the original size.
Potential reduce by 283.6 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. Obviously, Tom Green needs image optimization as it can save up to 283.6 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 363.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 363.3 kB or 68% of the original size.
Potential reduce by 260.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. Tomgreen.com needs all CSS files to be minified and compressed as it can save up to 260.1 kB or 83% of the original size.
Number of requests can be reduced by 34 (64%)
53
19
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tom Green. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
tomgreen.com
859 ms
style.css
55 ms
style.css
65 ms
custom.css
63 ms
jquery.lightbox-0.5.css
82 ms
css
83 ms
mediaelementplayer.min.css
61 ms
wp-mediaelement.css
58 ms
player.min.js
62 ms
jquery.js
60 ms
jquery-migrate.min.js
72 ms
upgrade.js
61 ms
ajaxupload.js
58 ms
superfish.js
56 ms
hoverIntent.js
56 ms
jquery.lightbox-0.5.js
56 ms
gigawatt_jquery.js
62 ms
masonry.js
62 ms
jquery.jplayer.min.js
1743 ms
selfhosted.js
1671 ms
swfobject.js
57 ms
swfaddress.js
55 ms
style.css
56 ms
mygp_geotags_geometatags.css
57 ms
plusone.js
203 ms
mediaelement-and-player.min.js
54 ms
wp-mediaelement.js
54 ms
widgets.js
54 ms
gumroad.js
55 ms
reset.css
75 ms
clearfix.css
75 ms
gumroad.js
180 ms
wp-emoji-release.min.js
87 ms
bnyVE1go2vs
321 ms
tXgfzxXUVsc
305 ms
mCyj0_N5oGM
304 ms
EFNrz8goEhs
304 ms
PdfztAY3qoU
296 ms
G-mK62LJ9zg
301 ms
ICHvyDNIFZY
349 ms
3-klvLR06lg
351 ms
texture.jpg
356 ms
fusion_grunge_logo.png
179 ms
nav-bullet.png
173 ms
sprite.png
172 ms
social-bg.png
171 ms
social-set.png
174 ms
form-bg.png
173 ms
search-bg.png
174 ms
cb=gapi.loaded_0
233 ms
analytics.js
118 ms
gumroad-overlay-70ff2a66d89f2a3434d169b884a285f03f2378f039b3cb3a1bee411240e7fc1e.js
179 ms
collect
48 ms
www-embed-player-vflRGs1ko.css
117 ms
www-embed-player.js
198 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
130 ms
ad_status.js
132 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
76 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
88 ms
overlay_page
8 ms
tomgreen.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
tomgreen.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
tomgreen.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 Tomgreen.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 Tomgreen.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.
tomgreen.com
Open Graph description is not detected on the main page of Tom Green. 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: