Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

craigsfire.com

Craig Issod – Tech, Business, Personal and Internet Consulting and Coaching | 40+ Years Experience at Making things happen

Page Load Speed

1.4 sec in total

First Response

187 ms

Resources Loaded

1 sec

Page Rendered

256 ms

craigsfire.com screenshot

About Website

Visit craigsfire.com now to see the best up-to-date Craig Sfire content and also check out these interesting facts you probably never knew about craigsfire.com

New! Starting in 2014, Craigsfire.com will be the home of my consulting company, CHI Associates, as well as a place I use to blog on business advice and experiences. CHI Associates Common Sense Intern...

Visit craigsfire.com

Key Findings

We analyzed Craigsfire.com page load time and found that the first response time was 187 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

craigsfire.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

craigsfire.com

187 ms

wp-emoji-release.min.js

63 ms

css

65 ms

style.css

104 ms

jetpack.css

150 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 34% of them (11 requests) were addressed to the original Craigsfire.com, 13% (4 requests) were made to Facebook.com and 9% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (188 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 223.7 kB (72%)

Content Size

310.7 kB

After Optimization

87.1 kB

In fact, the total size of Craigsfire.com main page is 310.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 157.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 29.9 kB

  • Original 41.1 kB
  • After minification 39.8 kB
  • After compression 11.3 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 29.9 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.3 kB
  • After minification 1.3 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. Craig Sfire images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 102.4 kB

  • Original 157.7 kB
  • After minification 156.3 kB
  • After compression 55.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 102.4 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 91.4 kB

  • Original 110.6 kB
  • After minification 97.7 kB
  • After compression 19.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. Craigsfire.com needs all CSS files to be minified and compressed as it can save up to 91.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (62%)

Requests Now

29

After Optimization

11

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

Accessibility Review

craigsfire.com accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Best Practices

craigsfire.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

SEO Factors

craigsfire.com SEO score

89

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

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 Craigsfire.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 Craigsfire.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

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