Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

thomaslawrence.com

Thomas Lawrence - Tech Enthusiast , Entrepreneur, Open Source Advocate, Social Media, Hot Sauce Addict and Public Speaker

Page Load Speed

3.6 sec in total

First Response

1.5 sec

Resources Loaded

1.9 sec

Page Rendered

163 ms

thomaslawrence.com screenshot

About Website

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

Tech Enthusiast , Entrepreneur, Open Source Advocate, Social Media, Hot Sauce Addict and Public Speaker

Visit thomaslawrence.com

Key Findings

We analyzed Thomaslawrence.com page load time and found that the first response time was 1.5 sec and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster. This domain responded with an error, which can significantly jeopardize Thomaslawrence.com rating and web reputation

Performance Metrics

thomaslawrence.com performance score

0

Network Requests Diagram

thomaslawrence.com

1534 ms

bootstrap.min.css

48 ms

style.css

40 ms

jquery.js

90 ms

bootstrap.min.js

56 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that all of those requests were addressed to Thomaslawrence.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Thomaslawrence.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 kB (0%)

Content Size

673.4 kB

After Optimization

671.5 kB

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

HTML Optimization

-65%

Potential reduce by 1.6 kB

  • Original 2.5 kB
  • After minification 2.3 kB
  • After compression 870 B

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 1.6 kB or 65% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 611.5 kB
  • After minification 611.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. Thomas Lawrence images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 102 B

  • Original 41.1 kB
  • After minification 41.1 kB
  • After compression 41.0 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

-1%

Potential reduce by 233 B

  • Original 18.3 kB
  • After minification 18.3 kB
  • After compression 18.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. Thomaslawrence.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thomas Lawrence. According to our analytics all requests are already optimized.

SEO Factors

thomaslawrence.com SEO score

0

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 Thomaslawrence.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 Thomaslawrence.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 description is not detected on the main page of Thomas Lawrence. 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: