Tools & Wizards About Us
jimestill.com screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

jimestill.com

CEO Blog - Time Leadership | Insights on Business, Life, and Productivity

Page Load Speed

23.7 sec in total

First Response

75 ms

Resources Loaded

20.1 sec

Page Rendered

3.5 sec

jimestill.com screenshot

About Website

Visit jimestill.com now to see the best up-to-date Jimestill content for Canada and also check out these interesting facts you probably never knew about jimestill.com

Read personal and professional insights from Jim Estill, CEO of Danby Appliances. Explore topics on leadership, productivity, innovation, time management, and personal growth.

Visit jimestill.com

Key Findings

We analyzed Jimestill.com page load time and found that the first response time was 75 ms and then it took 23.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

jimestill.com performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

jimestill.com

75 ms

www.jimestill.com

181 ms

blog_controls.css

58 ms

authorization.css

73 ms

backlink.js

75 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Jimestill.com, 24% (22 requests) were made to Accounts.google.com and 8% (7 requests) were made to Blogger.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Ir-na.amazon-adsystem.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.6 kB (15%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jimestill.com main page is 1.2 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 492.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 181.5 kB

  • Original 228.7 kB
  • After minification 218.1 kB
  • After compression 47.2 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 181.5 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 144 B

  • Original 492.7 kB
  • After minification 492.5 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. Jimestill images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 615 B

  • Original 492.9 kB
  • After minification 492.9 kB
  • After compression 492.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. This website has mostly compressed JavaScripts.

CSS Optimization

-44%

Potential reduce by 339 B

  • Original 775 B
  • After minification 735 B
  • After compression 436 B

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. Jimestill.com needs all CSS files to be minified and compressed as it can save up to 339 B or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (43%)

Requests Now

65

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jimestill.com

jimestill.com

75 ms

www.jimestill.com

www.jimestill.com

181 ms

blog_controls.css

blog_controls.css

58 ms

authorization.css

authorization.css

73 ms

backlink.js

backlink.js

75 ms

backlink_control.js

backlink_control.js

111 ms

style.css

style.css

134 ms

platform.js

platform.js

27 ms

show_ads.js

show_ads.js

81 ms

counter.js

counter.js

26 ms

authorization.css

authorization.css

71 ms

3334278262-classic.css

3334278262-classic.css

4 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

110 ms

bg-body.gif

bg-body.gif

110 ms

adsbygoogle.js

adsbygoogle.js

214 ms

icon18_email.gif

icon18_email.gif

159 ms

IMG_0828.jpg

IMG_0828.jpg

448 ms

IMG_20190426_214057.jpg

IMG_20190426_214057.jpg

406 ms

IMG_20190301_090518.jpg

IMG_20190301_090518.jpg

623 ms

IMG_20190301_090505.jpg

IMG_20190301_090505.jpg

398 ms

t.php

t.php

285 ms

a-logo-amazon.png

a-logo-amazon.png

72 ms

31TplCAQ5DL._AC_SR98,95_.jpg

31TplCAQ5DL._AC_SR98,95_.jpg

95 ms

IMG_20190228_082121.jpg

IMG_20190228_082121.jpg

800 ms

IMG_20190301_092950.jpg

IMG_20190301_092950.jpg

787 ms

P_20181222_121456%2B%25281%2529.jpg

P_20181222_121456%2B%25281%2529.jpg

807 ms

search-dark.png

search-dark.png

42 ms

cart.gif

cart.gif

35 ms

0

0

109 ms

0

0

112 ms

0

0

239 ms

0

0

239 ms

IMG_20190815_083930.jpg

IMG_20190815_083930.jpg

481 ms

jim_estill_CDN.jpg

jim_estill_CDN.jpg

264 ms

IMG_20190301_090416.jpg

IMG_20190301_090416.jpg

711 ms

sundae.jpeg

sundae.jpeg

711 ms

image1%2B%25283%2529.jpeg

image1%2B%25283%2529.jpeg

626 ms

P_20181222_123020.jpg

P_20181222_123020.jpg

658 ms

bg-headerdiv.gif

bg-headerdiv.gif

35 ms

header-03.gif

header-03.gif

39 ms

bg-header1.gif

bg-header1.gif

39 ms

bg-sidebar3.gif

bg-sidebar3.gif

54 ms

bg-profile3.gif

bg-profile3.gif

54 ms

bg-footer.gif

bg-footer.gif

54 ms

icon18_edit_allbkg.gif

icon18_edit_allbkg.gif

109 ms

ir

ir

19613 ms

json

json

62 ms

ga.js

ga.js

59 ms

navbar.g

navbar.g

70 ms

__utm.gif

__utm.gif

33 ms

__utm.gif

__utm.gif

21 ms

platform:gapi.iframes.style.common.js

platform:gapi.iframes.style.common.js

77 ms

icons_orange.png

icons_orange.png

12 ms

arrows-blue.png

arrows-blue.png

18 ms

time_leadership_cover.gif

time_leadership_cover.gif

1286 ms

show_ads_impl.js

show_ads_impl.js

247 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

56 ms

InteractiveLogin

InteractiveLogin

89 ms

InteractiveLogin

InteractiveLogin

77 ms

InteractiveLogin

InteractiveLogin

68 ms

InteractiveLogin

InteractiveLogin

76 ms

InteractiveLogin

InteractiveLogin

70 ms

InteractiveLogin

InteractiveLogin

87 ms

InteractiveLogin

InteractiveLogin

106 ms

InteractiveLogin

InteractiveLogin

147 ms

InteractiveLogin

InteractiveLogin

143 ms

InteractiveLogin

InteractiveLogin

141 ms

InteractiveLogin

InteractiveLogin

92 ms

identifier

identifier

192 ms

identifier

identifier

199 ms

identifier

identifier

210 ms

identifier

identifier

211 ms

identifier

identifier

227 ms

identifier

identifier

218 ms

identifier

identifier

310 ms

identifier

identifier

308 ms

identifier

identifier

282 ms

identifier

identifier

288 ms

identifier

identifier

298 ms

zrt_lookup.html

zrt_lookup.html

42 ms

ads

ads

552 ms

3957252553952054598

3957252553952054598

152 ms

abg_lite.js

abg_lite.js

35 ms

s

s

7 ms

window_focus.js

window_focus.js

34 ms

qs_click_protection.js

qs_click_protection.js

40 ms

ufs_web_display.js

ufs_web_display.js

32 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

149 ms

activeview

activeview

68 ms

GhmJCpBREX7wgGMT0ZiWZLwlRNdtIOd5PV2NPLMoOVM.js

GhmJCpBREX7wgGMT0ZiWZLwlRNdtIOd5PV2NPLMoOVM.js

6 ms

Accessibility Review

jimestill.com accessibility score

58

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jimestill.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

jimestill.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

jimestill.com

Open Graph description is not detected on the main page of Jimestill. 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: