Tools & Wizards About Us
syntax.fm screenshot

Report Summary

  • 55

    Performance

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

  • 97

    SEO

    Google-friendlier than
    91% of websites

syntax.fm

Syntax - Web Development Podcast

Page Load Speed

1.1 sec in total

First Response

23 ms

Resources Loaded

466 ms

Page Rendered

657 ms

syntax.fm screenshot

About Website

Visit syntax.fm now to see the best up-to-date Syntax content for United States and also check out these interesting facts you probably never knew about syntax.fm

Full Stack Web Developers Wes Bos and Scott Tolinski dive deep into web development, CSS, JavaScript, Frameworks, Typescript, Servers and more. Listen in 3 times a week!

Visit syntax.fm

Key Findings

We analyzed Syntax.fm page load time and found that the first response time was 23 ms and then it took 1.1 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

syntax.fm performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

syntax.fm

23 ms

syntax.fm

204 ms

script.js

36 ms

3.DP2y3HDZ.css

36 ms

style.Uf616igL.css

58 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 79% of them (27 requests) were addressed to the original Syntax.fm, 21% (7 requests) were made to Avatars.githubusercontent.com. The less responsive or slowest element that took the longest time to load (204 ms) belongs to the original domain Syntax.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.8 kB (20%)

Content Size

413.7 kB

After Optimization

329.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Syntax.fm main page is 413.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. 20% of websites need less resources to load. Images take 322.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 65.2 kB

  • Original 90.2 kB
  • After minification 89.6 kB
  • After compression 25.0 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 65.2 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 18.5 kB

  • Original 322.7 kB
  • After minification 304.2 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. Syntax images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 16 B

  • Original 764 B
  • After minification 764 B
  • After compression 748 B

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 13 (41%)

Requests Now

32

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

syntax.fm

syntax.fm

23 ms

syntax.fm

syntax.fm

204 ms

script.js

script.js

36 ms

3.DP2y3HDZ.css

3.DP2y3HDZ.css

36 ms

style.Uf616igL.css

style.Uf616igL.css

58 ms

Toaster.CDHw7-17.css

Toaster.CDHw7-17.css

58 ms

AlbumArt.B5k4mYSg.css

AlbumArt.B5k4mYSg.css

59 ms

Icon.UktXIfPo.css

Icon.UktXIfPo.css

58 ms

HairButton.Cf6ASgDa.css

HairButton.Cf6ASgDa.css

57 ms

Logo.DR9McsN1.css

Logo.DR9McsN1.css

58 ms

Header.BsScibQN.css

Header.BsScibQN.css

70 ms

Search.DjfUX5us.css

Search.DjfUX5us.css

67 ms

SearchBox.DWrXb4Xh.css

SearchBox.DWrXb4Xh.css

68 ms

11.DyS0yDga.css

11.DyS0yDga.css

71 ms

PodcastLinks.BXUiT1ab.css

PodcastLinks.BXUiT1ab.css

69 ms

ShowCard.DZkfCNWa.css

ShowCard.DZkfCNWa.css

68 ms

FacePile.BziPltzQ.css

FacePile.BziPltzQ.css

86 ms

176013

176013

26 ms

14241866

14241866

27 ms

80

80

21 ms

Grit%20Mask@2x.DjV8DBwn.png

Grit%20Mask@2x.DjV8DBwn.png

31 ms

rss.svg

rss.svg

45 ms

spotify.svg

spotify.svg

41 ms

itunes.jpg

itunes.jpg

36 ms

youtube.svg

youtube.svg

31 ms

overcast.jpg

overcast.jpg

34 ms

pocketcasts.jpg

pocketcasts.jpg

64 ms

amznMusic.png

amznMusic.png

65 ms

whitegrit.D_d8Ws2A.png

whitegrit.D_d8Ws2A.png

47 ms

grit.svg

grit.svg

129 ms

1134620

1134620

6 ms

1693164

1693164

7 ms

669383

669383

7 ms

18360871

18360871

6 ms

Accessibility Review

syntax.fm accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

syntax.fm best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

syntax.fm SEO score

97

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 Syntax.fm 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 Syntax.fm 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

syntax.fm

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