Tools & Wizards About Us
tommcfarlin.com screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

tommcfarlin.com

Tom McFarlin | Software Engineering in WordPress, PHP, and Backend Development

Page Load Speed

3.1 sec in total

First Response

119 ms

Resources Loaded

2.4 sec

Page Rendered

531 ms

tommcfarlin.com screenshot

About Website

Welcome to tommcfarlin.com homepage info - get ready to check Tom Mc Farlin best content for Pakistan right away, or after learning these important things about tommcfarlin.com

In the last decade, I’ve written extensively on software engineering in the context of WordPress, PHP, Databases, and other backend technology.

Visit tommcfarlin.com

Key Findings

We analyzed Tommcfarlin.com page load time and found that the first response time was 119 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

tommcfarlin.com performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.192

64/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

tommcfarlin.com

119 ms

tommcfarlin.com

1196 ms

wp-emoji-release.min.js

58 ms

style.css

104 ms

style.css

117 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 60% of them (30 requests) were addressed to the original Tommcfarlin.com, 16% (8 requests) were made to S3.buysellads.com and 6% (3 requests) were made to Js.stripe.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Tommcfarlin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.6 kB (29%)

Content Size

411.7 kB

After Optimization

293.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tommcfarlin.com main page is 411.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. 40% of websites need less resources to load. Images take 212.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 42.7 kB

  • Original 53.2 kB
  • After minification 48.4 kB
  • After compression 10.5 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 42.7 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 212.9 kB
  • After minification 211.9 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 Mc Farlin images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 74.8 kB

  • Original 145.5 kB
  • After minification 145.2 kB
  • After compression 70.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 74.8 kB or 51% of the original size.

CSS Optimization

-19%

Potential reduce by 30 B

  • Original 161 B
  • After minification 141 B
  • After compression 131 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. Tommcfarlin.com needs all CSS files to be minified and compressed as it can save up to 30 B or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (74%)

Requests Now

43

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tommcfarlin.com

tommcfarlin.com

119 ms

tommcfarlin.com

tommcfarlin.com

1196 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

58 ms

style.css

style.css

104 ms

style.css

style.css

117 ms

style.css

style.css

115 ms

media-queries.css

media-queries.css

140 ms

font-awesome.min.css

font-awesome.min.css

143 ms

flexslider.css

flexslider.css

142 ms

css

css

79 ms

style.min.css

style.min.css

153 ms

jetpack.css

jetpack.css

158 ms

wp-stripe-display.css

wp-stripe-display.css

163 ms

wp-stripe-widget.css

wp-stripe-widget.css

185 ms

wp-stripe-thickbox.css

wp-stripe-thickbox.css

184 ms

jquery.js

jquery.js

224 ms

jquery-migrate.min.js

jquery-migrate.min.js

195 ms

117 ms

wp-stripe.js

wp-stripe.js

196 ms

subscribe-form.css

subscribe-form.css

198 ms

devicepx-jetpack.js

devicepx-jetpack.js

143 ms

sharing-count.js

sharing-count.js

263 ms

custom.js

custom.js

262 ms

jquery.fitvids.js

jquery.fitvids.js

263 ms

jquery.flexslider.js

jquery.flexslider.js

265 ms

html5shiv.js

html5shiv.js

264 ms

thickbox.js

thickbox.js

295 ms

wp-embed.min.js

wp-embed.min.js

294 ms

subscribe-form.min.js

subscribe-form.min.js

294 ms

e-201609.js

e-201609.js

49 ms

initialize-wordpress-plugins.jpg

initialize-wordpress-plugins.jpg

186 ms

permission-scheme.png

permission-scheme.png

224 ms

bsa.js

bsa.js

47 ms

analytics.js

analytics.js

165 ms

Pru33qjShpZSmG3z6VYwnaCWcynf_cDxXwCLxiixG1c.ttf

Pru33qjShpZSmG3z6VYwnaCWcynf_cDxXwCLxiixG1c.ttf

171 ms

5M21SdFLkD52QavfmHs6cA.ttf

5M21SdFLkD52QavfmHs6cA.ttf

192 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

148 ms

loadingAnimation.gif

loadingAnimation.gif

48 ms

s_99a8d2230275daddb56decfa1412d72a.js

s_99a8d2230275daddb56decfa1412d72a.js

12 ms

g.gif

g.gif

26 ms

channel.html

channel.html

23 ms

pro.js

pro.js

11 ms

collect

collect

16 ms

15 ms

386 ms

245426-1415296051.jpeg

245426-1415296051.jpeg

10 ms

263230-1427137069.jpg

263230-1427137069.jpg

3 ms

243103-1414001265.jpeg

243103-1414001265.jpeg

5 ms

206098-1390446243.png

206098-1390446243.png

254 ms

223419-1400702707.jpg

223419-1400702707.jpg

21 ms

Accessibility Review

tommcfarlin.com accessibility score

91

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.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

tommcfarlin.com SEO score

93

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

    EN

  • Encoding

    UTF-8

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

tommcfarlin.com

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