Tools & Wizards About Us
cookins.net screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    83% 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

  • 93

    SEO

    Google-friendlier than
    84% of websites

cookins.net

Insurance Agency in Butler, MO | Cook Insurance Agency, Inc.

Page Load Speed

874 ms in total

First Response

60 ms

Resources Loaded

586 ms

Page Rendered

228 ms

cookins.net screenshot

About Website

Welcome to cookins.net homepage info - get ready to check Cook Ins best content right away, or after learning these important things about cookins.net

Cook Insurance Agency, Inc. is proud to serve the insurance needs of Butler and all of MO. Let us help you find the right insurance to meet your needs. Contact us now for quick, competitive quotes!

Visit cookins.net

Key Findings

We analyzed Cookins.net page load time and found that the first response time was 60 ms and then it took 814 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

cookins.net performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

cookins.net

60 ms

cookins.net

24 ms

webfont.js

22 ms

styles.min.css

6 ms

style.css

74 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 58% of them (18 requests) were addressed to the original Cookins.net, 13% (4 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (442 ms) relates to the external source S3-us-west-2.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.1 kB (11%)

Content Size

1.0 MB

After Optimization

896.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cookins.net main page is 1.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. 35% of websites need less resources to load. Images take 843.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 20.7 kB

  • Original 25.8 kB
  • After minification 21.8 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 4.0 kB, which is 15% 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 20.7 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 47.2 kB

  • Original 843.6 kB
  • After minification 796.4 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. Cook Ins images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 43.8 kB

  • Original 125.5 kB
  • After minification 120.1 kB
  • After compression 81.7 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 43.8 kB or 35% of the original size.

CSS Optimization

-3%

Potential reduce by 437 B

  • Original 13.5 kB
  • After minification 13.5 kB
  • After compression 13.0 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. Cookins.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (25%)

Requests Now

24

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cookins.net

cookins.net

60 ms

cookins.net

cookins.net

24 ms

webfont.js

webfont.js

22 ms

styles.min.css

styles.min.css

6 ms

style.css

style.css

74 ms

s_code.js

s_code.js

442 ms

jquery.min.js

jquery.min.js

23 ms

snap.min.js

snap.min.js

84 ms

scripts.min.js

scripts.min.js

84 ms

css

css

29 ms

analytics.js

analytics.js

116 ms

staticmap

staticmap

275 ms

logo.png

logo.png

99 ms

banner-image.jpg

banner-image.jpg

129 ms

banner-content-shape.png

banner-content-shape.png

99 ms

5-Tips-for-Safe-Driving-in-the-Winter_FI.jpg

5-Tips-for-Safe-Driving-in-the-Winter_FI.jpg

98 ms

December-2023_FI.jpg

December-2023_FI.jpg

98 ms

November-2023_FI.jpg

November-2023_FI.jpg

184 ms

Acuity.png

Acuity.png

127 ms

round_ao_logo.jpg

round_ao_logo.jpg

186 ms

NationWide.jpg

NationWide.jpg

127 ms

Safeco.png

Safeco.png

157 ms

action-shape.png

action-shape.png

157 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

39 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

61 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

64 ms

sitebuilder-icons.ttf

sitebuilder-icons.ttf

66 ms

collect

collect

30 ms

js

js

78 ms

s92628821937832

s92628821937832

7 ms

Accessibility Review

cookins.net accessibility score

97

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.

Best Practices

cookins.net 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

cookins.net SEO score

93

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

cookins.net

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