Tools & Wizards About Us
pogue.blogs.nytimes.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

pogue.blogs.nytimes.com

Technology - Pogue's Posts Blog - The New York Times

Page Load Speed

1.8 sec in total

First Response

20 ms

Resources Loaded

972 ms

Page Rendered

827 ms

pogue.blogs.nytimes.com screenshot

About Website

Welcome to pogue.blogs.nytimes.com homepage info - get ready to check Pogue Blog S Ny Times best content for United States right away, or after learning these important things about pogue.blogs.nytimes.com

Reviews and quick hits from David Pogue, whose technology column has appeared each Thursday in The Times since 2000.

Visit pogue.blogs.nytimes.com

Key Findings

We analyzed Pogue.blogs.nytimes.com page load time and found that the first response time was 20 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

pogue.blogs.nytimes.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,360 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.126

83/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

pogue.blogs.nytimes.com

20 ms

101 ms

nyt-capsule.js

5 ms

styles.css

25 ms

universal.css

42 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pogue.blogs.nytimes.com, 25% (19 requests) were made to Static01.nyt.com and 19% (14 requests) were made to Int.nyt.com. The less responsive or slowest element that took the longest time to load (345 ms) relates to the external source A.dev.nytimes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 352.8 kB (22%)

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pogue.blogs.nytimes.com main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 871.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 164.6 kB

  • Original 198.0 kB
  • After minification 167.2 kB
  • After compression 33.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. This page needs HTML code to be minified as it can gain 30.8 kB, which is 16% 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 164.6 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 50.5 kB

  • Original 871.1 kB
  • After minification 820.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. Pogue Blog S Ny Times images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 137.5 kB

  • Original 358.0 kB
  • After minification 357.8 kB
  • After compression 220.5 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 137.5 kB or 38% of the original size.

CSS Optimization

-0%

Potential reduce by 151 B

  • Original 151.4 kB
  • After minification 151.4 kB
  • After compression 151.2 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. Pogue.blogs.nytimes.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (45%)

Requests Now

55

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pogue Blog S Ny 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 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pogue.blogs.nytimes.com

pogue.blogs.nytimes.com

20 ms

101 ms

nyt-capsule.js

nyt-capsule.js

5 ms

styles.css

styles.css

25 ms

universal.css

universal.css

42 ms

framework.js

framework.js

52 ms

nyt-capsule.css

nyt-capsule.css

6 ms

nyt5-capsule-override.css

nyt5-capsule-override.css

16 ms

widgets.js

widgets.js

93 ms

nyt-blogs-capsule.js

nyt-blogs-capsule.js

96 ms

zam5nzz.js

zam5nzz.js

153 ms

fonts.css

fonts.css

32 ms

styles-print.css

styles-print.css

6 ms

main.js

main.js

12 ms

sprite-no-repeat.svg

sprite-no-repeat.svg

75 ms

pogue_main.png

pogue_main.png

101 ms

17fddp-blog480.png

17fddp-blog480.png

96 ms

10fddp-1-blog480.jpg

10fddp-1-blog480.jpg

95 ms

03fddp-kindle-blog480.png

03fddp-kindle-blog480.png

157 ms

26fddp-fingerprint-blog480.jpg

26fddp-fingerprint-blog480.jpg

112 ms

17pogue-iphones-blog480.jpg

17pogue-iphones-blog480.jpg

128 ms

12pogue-air-blog480.jpg

12pogue-air-blog480.jpg

113 ms

11pogue-5s-blog480.jpg

11pogue-5s-blog480.jpg

113 ms

05pogue-peeq-blog480.png

05pogue-peeq-blog480.png

158 ms

03pogue-ballmer-elop-blog480.jpg

03pogue-ballmer-elop-blog480.jpg

157 ms

29fddp-articleInline.jpg

29fddp-articleInline.jpg

159 ms

26pogue-voice-blog480.jpg

26pogue-voice-blog480.jpg

160 ms

FDDP_inlineheader.jpg

FDDP_inlineheader.jpg

159 ms

15fddp-glasses-blog480.png

15fddp-glasses-blog480.png

161 ms

share_logos_vertical_40x40.png

share_logos_vertical_40x40.png

160 ms

nyt-logo-185x26.svg

nyt-logo-185x26.svg

93 ms

nyt-logo-185x26.png

nyt-logo-185x26.png

93 ms

hosts.js

hosts.js

94 ms

mtr.js

mtr.js

120 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

75 ms

zam5nzz.css

zam5nzz.css

17 ms

main.js

main.js

65 ms

tracking.js

tracking.js

68 ms

userinfo-v3.jsonp

userinfo-v3.jsonp

81 ms

settings

settings

293 ms

localstorage.html

localstorage.html

173 ms

nyt-franklin-300-normal.woff

nyt-franklin-300-normal.woff

106 ms

nyt-franklin-500-normal.woff

nyt-franklin-500-normal.woff

138 ms

nyt-franklin-700-normal.woff

nyt-franklin-700-normal.woff

136 ms

nyt-cheltenham-400-normal.woff

nyt-cheltenham-400-normal.woff

151 ms

nyt-cheltenham-500-normal.woff

nyt-cheltenham-500-normal.woff

198 ms

nyt-cheltenham-300-normal.woff

nyt-cheltenham-300-normal.woff

201 ms

nyt-cheltenham-200-normal.woff

nyt-cheltenham-200-normal.woff

200 ms

nyt-cheltenham-700-normal.woff

nyt-cheltenham-700-normal.woff

201 ms

nyt-cheltenham-sh-400-normal.woff

nyt-cheltenham-sh-400-normal.woff

228 ms

nyt-cheltenham-sh-700-normal.woff

nyt-cheltenham-sh-700-normal.woff

201 ms

nyt-cheltenham-300-italic.woff

nyt-cheltenham-300-italic.woff

222 ms

nyt-cheltenham-700-italic.woff

nyt-cheltenham-700-italic.woff

226 ms

gtm.js

gtm.js

248 ms

data-layer

data-layer

345 ms

cropped-1.jpg

cropped-1.jpg

258 ms

common.js

common.js

127 ms

amzn_ads.js

amzn_ads.js

241 ms

notifications.json

notifications.json

55 ms

global.json

global.json

55 ms

flat.json

flat.json

92 ms

user.json

user.json

217 ms

requestHandler

requestHandler

99 ms

liveupdates.js

liveupdates.js

97 ms

ad-view-manager.js

ad-view-manager.js

58 ms

vhs.js

vhs.js

87 ms

tweet.d7aeb21a88e025d2ea5f5431a103f586.js

tweet.d7aeb21a88e025d2ea5f5431a103f586.js

14 ms

active

active

28 ms

bid

bid

257 ms

Tweet.html

Tweet.html

6 ms

Tweet.html

Tweet.html

8 ms

Tweet.html

Tweet.html

10 ms

embed.runtime.d4fdbaa43d8afce29068.js

embed.runtime.d4fdbaa43d8afce29068.js

7 ms

embed.9449.78398904051446294e3d.js

embed.9449.78398904051446294e3d.js

12 ms

embed.Tweet.02ab0848482b3e69ec95.js

embed.Tweet.02ab0848482b3e69ec95.js

7 ms

Accessibility Review

pogue.blogs.nytimes.com accessibility score

93

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

pogue.blogs.nytimes.com best practices score

67

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pogue.blogs.nytimes.com SEO score

79

Search Engine Optimization Advices

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 Pogue.blogs.nytimes.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 Pogue.blogs.nytimes.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

pogue.blogs.nytimes.com

Open Graph description is not detected on the main page of Pogue Blog S Ny 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: