Tools & Wizards About Us
matthewteller.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

matthewteller.com

Matthew Teller - writer, journalist, broadcaster & documentary-maker

Page Load Speed

1.8 sec in total

First Response

48 ms

Resources Loaded

1.4 sec

Page Rendered

360 ms

matthewteller.com screenshot

About Website

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

Matthew Teller writes and broadcasts for the BBC and other media outlets around the world. He is an author, travel writer and documentary-maker.

Visit matthewteller.com

Key Findings

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

Performance Metrics

matthewteller.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

matthewteller.com

48 ms

www.matthewteller.com

130 ms

rko4kag.js

106 ms

main.css

21 ms

site.min.js

32 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 50% of them (17 requests) were addressed to the original Matthewteller.com, 26% (9 requests) were made to Use.typekit.net and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (332 ms) relates to the external source C.statcounter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.1 kB (3%)

Content Size

941.8 kB

After Optimization

909.6 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-75%

Potential reduce by 30.3 kB

  • Original 40.7 kB
  • After minification 40.5 kB
  • After compression 10.4 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 30.3 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 694 B

  • Original 649.3 kB
  • After minification 648.6 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. Matthew Teller images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

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

Requests Breakdown

Number of requests can be reduced by 7 (41%)

Requests Now

17

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

matthewteller.com

matthewteller.com

48 ms

www.matthewteller.com

www.matthewteller.com

130 ms

rko4kag.js

rko4kag.js

106 ms

main.css

main.css

21 ms

site.min.js

site.min.js

32 ms

email-decode.min.js

email-decode.min.js

23 ms

api.js

api.js

43 ms

counter.js

counter.js

38 ms

Daybreak-in-Gaza-front-cover-500x802.jpg

Daybreak-in-Gaza-front-cover-500x802.jpg

263 ms

t.php

t.php

332 ms

analytics.js

analytics.js

282 ms

Nine-Quarters-of-Jerusalem-final-cover-500x802.jpg

Nine-Quarters-of-Jerusalem-final-cover-500x802.jpg

74 ms

Jerusalem-US-cover-500x750.jpg

Jerusalem-US-cover-500x750.jpg

73 ms

nine-1905x1280.jpg

nine-1905x1280.jpg

94 ms

bw-500x500.jpg

bw-500x500.jpg

93 ms

recaptcha__en.js

recaptcha__en.js

105 ms

CalibreLight.woff

CalibreLight.woff

154 ms

Calibre-Regular.woff

Calibre-Regular.woff

156 ms

FontAwesomeBrands-Regular-webfont.woff

FontAwesomeBrands-Regular-webfont.woff

155 ms

BlackTie-Regular-webfont.woff

BlackTie-Regular-webfont.woff

155 ms

BlackTie-Light-webfont.woff

BlackTie-Light-webfont.woff

178 ms

BlackTie-Bold-webfont.woff

BlackTie-Bold-webfont.woff

178 ms

BlackTie-Solid-webfont.woff

BlackTie-Solid-webfont.woff

178 ms

d

d

14 ms

d

d

43 ms

d

d

43 ms

d

d

72 ms

d

d

71 ms

d

d

71 ms

d

d

70 ms

d

d

91 ms

p.gif

p.gif

115 ms

collect

collect

36 ms

js

js

98 ms

Accessibility Review

matthewteller.com accessibility score

84

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

Links do not have a discernible name

Best Practices

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

matthewteller.com SEO score

93

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

Links do not have descriptive text

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Matthewteller.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Matthewteller.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

matthewteller.com

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