Tools & Wizards About Us
sethfiegerman.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

sethfiegerman.com

Seth Fiegerman

Page Load Speed

1.1 sec in total

First Response

27 ms

Resources Loaded

808 ms

Page Rendered

236 ms

sethfiegerman.com screenshot

About Website

Welcome to sethfiegerman.com homepage info - get ready to check Seth Fiegerman best content right away, or after learning these important things about sethfiegerman.com

CNN reporter covering the big tech companies. Editor of OpeningLines.org, a blog focused on how writers and artists got their start. Tweeter of snarky commentary.

Visit sethfiegerman.com

Key Findings

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

Performance Metrics

sethfiegerman.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

sethfiegerman.com

27 ms

sethfiegerman.com

188 ms

pre_tumblelog.js

67 ms

index.build.css

72 ms

jquery.min.js

73 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Sethfiegerman.com, 36% (15 requests) were made to Assets.tumblr.com and 17% (7 requests) were made to 64.media.tumblr.com. The less responsive or slowest element that took the longest time to load (370 ms) relates to the external source 64.media.tumblr.com.

Page Optimization Overview & Recommendations

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

Content Size

353.7 kB

After Optimization

235.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 109.8 kB

  • Original 129.4 kB
  • After minification 107.7 kB
  • After compression 19.6 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. This page needs HTML code to be minified as it can gain 21.7 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 109.8 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 6.2 kB

  • Original 197.2 kB
  • After minification 191.0 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. Seth Fiegerman images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 324 B

  • Original 16.2 kB
  • After minification 16.2 kB
  • After compression 15.9 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

-21%

Potential reduce by 2.3 kB

  • Original 10.9 kB
  • After minification 10.9 kB
  • After compression 8.6 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. Sethfiegerman.com needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 21% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sethfiegerman.com

sethfiegerman.com

27 ms

sethfiegerman.com

sethfiegerman.com

188 ms

pre_tumblelog.js

pre_tumblelog.js

67 ms

index.build.css

index.build.css

72 ms

jquery.min.js

jquery.min.js

73 ms

underscore-min.js

underscore-min.js

101 ms

masonry.pkgd.js

masonry.pkgd.js

107 ms

spectator.min.js

spectator.min.js

91 ms

spectator.css

spectator.css

91 ms

bilmur.min.js

bilmur.min.js

91 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

69 ms

stylesheet.css

stylesheet.css

70 ms

stylesheet.css

stylesheet.css

84 ms

stylesheet.css

stylesheet.css

84 ms

index.build.js

index.build.js

88 ms

tumblr_static_146i843f42rk0gkc0w8c40wcs.jpg

tumblr_static_146i843f42rk0gkc0w8c40wcs.jpg

261 ms

tumblr_one28bMYPN1r8yubno1_500.png

tumblr_one28bMYPN1r8yubno1_500.png

183 ms

hqdefault.jpg

hqdefault.jpg

305 ms

impixu

impixu

171 ms

g.gif

g.gif

118 ms

featured

featured

216 ms

tumblr_one20cF4791r8yubno1_500.png

tumblr_one20cF4791r8yubno1_500.png

89 ms

tumblr_one19vlgAq1r8yubno1_r1_500.png

tumblr_one19vlgAq1r8yubno1_r1_500.png

90 ms

tumblr_one11bqnkS1r8yubno1_500.png

tumblr_one11bqnkS1r8yubno1_500.png

249 ms

tumblr_one0sniykU1r8yubno1_500.png

tumblr_one0sniykU1r8yubno1_500.png

90 ms

tumblr_o8yxy3bUwt1r8yubno1_500.jpg

tumblr_o8yxy3bUwt1r8yubno1_500.jpg

179 ms

tumblr_o8bnvrzoW41r8yubno1_500.png

tumblr_o8bnvrzoW41r8yubno1_500.png

370 ms

impixu

impixu

74 ms

spectator.png

spectator.png

67 ms

analytics.html

analytics.html

11 ms

login_check.html

login_check.html

9 ms

CapitaReg-webfont.woff

CapitaReg-webfont.woff

64 ms

CapitaBol-webfont.woff

CapitaBol-webfont.woff

64 ms

g.gif

g.gif

39 ms

consent

consent

57 ms

spectator.png

spectator.png

17 ms

cs.js

cs.js

2 ms

header.build.js

header.build.js

2 ms

exceptions.js

exceptions.js

3 ms

index.build.js

index.build.js

11 ms

cdn.json

cdn.json

27 ms

g.gif

g.gif

3 ms

Accessibility Review

sethfiegerman.com accessibility score

61

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sethfiegerman.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

sethfiegerman.com SEO score

91

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

High

Tap targets are not sized appropriately

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

sethfiegerman.com

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