Tools & Wizards About Us
tomclark.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

tomclark.com

TOM CLARK - Tom Clark Comedian

Page Load Speed

1.7 sec in total

First Response

234 ms

Resources Loaded

1.2 sec

Page Rendered

272 ms

tomclark.com screenshot

About Website

Welcome to tomclark.com homepage info - get ready to check TOM CLARK best content right away, or after learning these important things about tomclark.com

Tom Clark Comedian

Visit tomclark.com

Key Findings

We analyzed Tomclark.com page load time and found that the first response time was 234 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. This domain responded with an error, which can significantly jeopardize Tomclark.com rating and web reputation

Performance Metrics

tomclark.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value22.3 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.443

21/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

tomclark.com

234 ms

www.tomclark.com

424 ms

sites.css

81 ms

fancybox.css

58 ms

social-icons.css

107 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 22% of them (8 requests) were addressed to the original Tomclark.com, 22% (8 requests) were made to Cdn2.editmysite.com and 11% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (424 ms) belongs to the original domain Tomclark.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (55%)

Content Size

2.0 MB

After Optimization

906.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tomclark.com main page is 2.0 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. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 36.8 kB

  • Original 45.4 kB
  • After minification 44.9 kB
  • After compression 8.6 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 36.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 101 B

  • Original 444.1 kB
  • After minification 444.0 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. TOM CLARK images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 755.0 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 403.4 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 755.0 kB or 65% of the original size.

CSS Optimization

-86%

Potential reduce by 307.2 kB

  • Original 358.0 kB
  • After minification 354.1 kB
  • After compression 50.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. Tomclark.com needs all CSS files to be minified and compressed as it can save up to 307.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (66%)

Requests Now

32

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TOM CLARK. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tomclark.com

tomclark.com

234 ms

www.tomclark.com

www.tomclark.com

424 ms

sites.css

sites.css

81 ms

fancybox.css

fancybox.css

58 ms

social-icons.css

social-icons.css

107 ms

main_style.css

main_style.css

237 ms

css

css

26 ms

css

css

41 ms

templateArtifacts.js

templateArtifacts.js

165 ms

jquery.min.js

jquery.min.js

73 ms

main.js

main.js

194 ms

commerce-core.js

commerce-core.js

77 ms

main-commerce-browse.js

main-commerce-browse.js

56 ms

ftl.js

ftl.js

147 ms

stl.js

stl.js

58 ms

plugins.js

plugins.js

258 ms

custom.js

custom.js

189 ms

mobile.js

mobile.js

186 ms

1729895954.jpg

1729895954.jpg

420 ms

64420150

64420150

83 ms

7378942_orig.jpg

7378942_orig.jpg

289 ms

analytics.js

analytics.js

49 ms

sp.js

sp.js

31 ms

wsocial.woff

wsocial.woff

36 ms

player.js

player.js

145 ms

player.css

player.css

112 ms

ga.js

ga.js

120 ms

vuid.min.js

vuid.min.js

119 ms

ga.js

ga.js

45 ms

quant.js

quant.js

41 ms

pixel;r=2109159397;a=p-0dYLvhSGGqUWo;labels=l10%2Cu51088491.u51088491s960164642775882111;fpan=1;fpa=P0-1862656301-1458305992174;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458305992174;tzo=-180;ref=;url=http%3A%2F%2Fwww.tomclark.com%2F;ogl=site_name.Tom%20Clark%20-%20Comedian%252C%20Actor%252C%20Writer%2Ctitle.Tom%20Clark%20Comedian%2Cdescription.Tom%20Clark%20Comedian%2Cimage.http%3A%2F%2Fwww%252Etomclark%252Ecom%2Fuploads%2F5%2F1%2F0%2F8%2F51088491%2F7378942_orig%252Ejpg%2Curl.http%3A%2F%2Fwww%252Etomclark%252Ecom%2F

pixel;r=2109159397;a=p-0dYLvhSGGqUWo;labels=l10%2Cu51088491.u51088491s960164642775882111;fpan=1;fpa=P0-1862656301-1458305992174;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458305992174;tzo=-180;ref=;url=http%3A%2F%2Fwww.tomclark.com%2F;ogl=site_name.Tom%20Clark%20-%20Comedian%252C%20Actor%252C%20Writer%2Ctitle.Tom%20Clark%20Comedian%2Cdescription.Tom%20Clark%20Comedian%2Cimage.http%3A%2F%2Fwww%252Etomclark%252Ecom%2Fuploads%2F5%2F1%2F0%2F8%2F51088491%2F7378942_orig%252Ejpg%2Curl.http%3A%2F%2Fwww%252Etomclark%252Ecom%2F

26 ms

__utm.gif

__utm.gif

40 ms

__utm.gif

__utm.gif

69 ms

proxy.html

proxy.html

42 ms

435061711.jpg

435061711.jpg

74 ms

3835848_60x60.jpg

3835848_60x60.jpg

51 ms

Accessibility Review

tomclark.com accessibility score

97

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

Best Practices

tomclark.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tomclark.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomclark.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 Tomclark.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.

Social Sharing Optimization

tomclark.com

Open Graph data is detected on the main page of TOM CLARK. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: