Tools & Wizards About Us
blogs.seattletimes.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

blogs.seattletimes.com

The Seattle Times | Local news, sports, business, politics, entertainment, travel, restaurants and opinion for Seattle and the Pacific Northwest.

Page Load Speed

1.4 sec in total

First Response

14 ms

Resources Loaded

1.2 sec

Page Rendered

222 ms

blogs.seattletimes.com screenshot

About Website

Visit blogs.seattletimes.com now to see the best up-to-date Blogs Seattle Times content for United States and also check out these interesting facts you probably never knew about blogs.seattletimes.com

Local news, sports, business, politics, entertainment, travel, restaurants and opinion for Seattle and the Pacific Northwest.

Visit blogs.seattletimes.com

Key Findings

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

Performance Metrics

blogs.seattletimes.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value6,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value28.9 s

0/100

10%

Network Requests Diagram

blogs.seattletimes.com

14 ms

www.seattletimes.com

803 ms

htlbid.css

79 ms

lty1dar.css

61 ms

chartbeat_mab.js

49 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Blogs.seattletimes.com, 42% (13 requests) were made to Seattletimes.com and 16% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (803 ms) relates to the external source Seattletimes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (78%)

Content Size

1.7 MB

After Optimization

370.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blogs.seattletimes.com main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 703.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 612.3 kB

  • Original 703.4 kB
  • After minification 700.8 kB
  • After compression 91.1 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 612.3 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 6.5 kB
  • After minification 6.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. Blogs Seattle Times images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 443.0 kB

  • Original 662.2 kB
  • After minification 662.2 kB
  • After compression 219.2 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 443.0 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 260.1 kB

  • Original 313.9 kB
  • After minification 313.9 kB
  • After compression 53.8 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. Blogs.seattletimes.com needs all CSS files to be minified and compressed as it can save up to 260.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (84%)

Requests Now

25

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blogs.seattletimes.com

blogs.seattletimes.com

14 ms

www.seattletimes.com

www.seattletimes.com

803 ms

htlbid.css

htlbid.css

79 ms

lty1dar.css

lty1dar.css

61 ms

chartbeat_mab.js

chartbeat_mab.js

49 ms

25075460524.js

25075460524.js

58 ms

styles.min.css

styles.min.css

55 ms

style.css

style.css

58 ms

css

css

67 ms

shortcodes-public.css

shortcodes-public.css

54 ms

st-blocking-bundle.js

st-blocking-bundle.js

56 ms

otSDKStub.js

otSDKStub.js

69 ms

st-spruce-bundle.js

st-spruce-bundle.js

31 ms

st-spruce-app.js

st-spruce-app.js

56 ms

bundle.min.js

bundle.min.js

37 ms

st-sitewide-bundle.js

st-sitewide-bundle.js

42 ms

st-advertising-bundle.js

st-advertising-bundle.js

33 ms

client

client

72 ms

st-user-messaging-main-bundle.js

st-user-messaging-main-bundle.js

36 ms

p.css

p.css

35 ms

gtm.js

gtm.js

232 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

117 ms

otCCPAiab.js

otCCPAiab.js

87 ms

footer-temp.png

footer-temp.png

40 ms

4bed09d4-1fd8-4251-bf32-d5e876bff7d5.json

4bed09d4-1fd8-4251-bf32-d5e876bff7d5.json

50 ms

d

d

63 ms

d

d

95 ms

d

d

36 ms

d

d

20 ms

dnsfeed

dnsfeed

78 ms

location

location

94 ms

Accessibility Review

blogs.seattletimes.com accessibility score

89

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

Image elements do not have [alt] attributes

Best Practices

blogs.seattletimes.com 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

blogs.seattletimes.com SEO score

92

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

Image elements do not have [alt] attributes

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 Blogs.seattletimes.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 Blogs.seattletimes.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

blogs.seattletimes.com

Open Graph description is not detected on the main page of Blogs Seattle Times. 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: