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

Report Summary

  • 62

    Performance

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

globespotters.blogs.nytimes.com

Globespotters - Travel Tips, News and Recommendations - Globespotters Blog - The New York Times

Page Load Speed

1.5 sec in total

First Response

22 ms

Resources Loaded

809 ms

Page Rendered

664 ms

globespotters.blogs.nytimes.com screenshot

About Website

Click here to check amazing Globespotters Blog S Ny Times content for United States. Otherwise, check out these important facts you probably never knew about globespotters.blogs.nytimes.com

With travel tips, news and recommendations, The New York Times's Globespotters blog provides up-to-the-minute tips and recommendations about the cities where we live and visit.

Visit globespotters.blogs.nytimes.com

Key Findings

We analyzed Globespotters.blogs.nytimes.com page load time and found that the first response time was 22 ms and then it took 1.5 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

globespotters.blogs.nytimes.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

globespotters.blogs.nytimes.com

22 ms

136 ms

nyt-capsule.js

4 ms

styles.css

115 ms

universal.css

107 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Globespotters.blogs.nytimes.com, 22% (16 requests) were made to Static01.nyt.com and 22% (16 requests) were made to A1.nyt.com. The less responsive or slowest element that took the longest time to load (164 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.3 kB (21%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Globespotters.blogs.nytimes.com main page is 1.3 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. 65% of websites need less resources to load. Images take 604.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 122.9 kB

  • Original 148.7 kB
  • After minification 133.6 kB
  • After compression 25.8 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 122.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 800 B

  • Original 604.9 kB
  • After minification 604.1 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. Globespotters 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. Globespotters.blogs.nytimes.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (50%)

Requests Now

40

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

globespotters.blogs.nytimes.com

globespotters.blogs.nytimes.com

22 ms

136 ms

nyt-capsule.js

nyt-capsule.js

4 ms

styles.css

styles.css

115 ms

universal.css

universal.css

107 ms

framework.js

framework.js

137 ms

nyt-capsule.css

nyt-capsule.css

5 ms

nyt5-capsule-override.css

nyt5-capsule-override.css

6 ms

nyt-blogs-capsule.js

nyt-blogs-capsule.js

17 ms

zam5nzz.js

zam5nzz.js

26 ms

fonts.css

fonts.css

31 ms

styles-print.css

styles-print.css

6 ms

main.js

main.js

9 ms

zam5nzz.css

zam5nzz.css

5 ms

sprite-no-repeat.svg

sprite-no-repeat.svg

71 ms

blogSpan.jpg

blogSpan.jpg

98 ms

nyt-logo-185x26.svg

nyt-logo-185x26.svg

86 ms

nyt-logo-185x26.png

nyt-logo-185x26.png

85 ms

blogSpan.jpg

blogSpan.jpg

94 ms

blogSpan.jpg

blogSpan.jpg

97 ms

blogSpan.jpg

blogSpan.jpg

109 ms

blogSpan.jpg

blogSpan.jpg

135 ms

blogSpan.jpg

blogSpan.jpg

113 ms

blogSpan.jpg

blogSpan.jpg

112 ms

articleInline.jpg

articleInline.jpg

108 ms

blogSpan.jpg

blogSpan.jpg

110 ms

articleInline.jpg

articleInline.jpg

143 ms

articleInline.jpg

articleInline.jpg

135 ms

blogSpan.jpg

blogSpan.jpg

142 ms

hosts.js

hosts.js

106 ms

mtr.js

mtr.js

85 ms

nyt-franklin-300-normal.woff

nyt-franklin-300-normal.woff

24 ms

nyt-franklin-500-normal.woff

nyt-franklin-500-normal.woff

27 ms

nyt-franklin-700-normal.woff

nyt-franklin-700-normal.woff

51 ms

nyt-cheltenham-400-normal.woff

nyt-cheltenham-400-normal.woff

53 ms

nyt-cheltenham-500-normal.woff

nyt-cheltenham-500-normal.woff

56 ms

nyt-cheltenham-300-normal.woff

nyt-cheltenham-300-normal.woff

53 ms

nyt-cheltenham-200-normal.woff

nyt-cheltenham-200-normal.woff

55 ms

nyt-cheltenham-700-normal.woff

nyt-cheltenham-700-normal.woff

53 ms

karnak-normal-400.woff

karnak-normal-400.woff

19 ms

karnak-normal-500.woff

karnak-normal-500.woff

25 ms

karnak-cursive-500.woff

karnak-cursive-500.woff

52 ms

karnak-normal-300.woff

karnak-normal-300.woff

55 ms

karnak-cursive-300.woff

karnak-cursive-300.woff

57 ms

karnak-normal-200.woff

karnak-normal-200.woff

59 ms

karnak-cursive-200.woff

karnak-cursive-200.woff

55 ms

karnak-normal-100.woff

karnak-normal-100.woff

52 ms

karnak-cursive-100.woff

karnak-cursive-100.woff

60 ms

karnak-normal-600.woff

karnak-normal-600.woff

60 ms

karnak-cursive-600.woff

karnak-cursive-600.woff

61 ms

karnak-normal-700.woff

karnak-normal-700.woff

60 ms

karnak-cursive-700.woff

karnak-cursive-700.woff

61 ms

karnak-normal-900.woff

karnak-normal-900.woff

62 ms

karnak-cursive-900.woff

karnak-cursive-900.woff

62 ms

nyt-cheltenham-sh-400-normal.woff

nyt-cheltenham-sh-400-normal.woff

57 ms

nyt-cheltenham-sh-700-normal.woff

nyt-cheltenham-sh-700-normal.woff

58 ms

main.js

main.js

45 ms

tracking.js

tracking.js

55 ms

userinfo-v3.jsonp

userinfo-v3.jsonp

144 ms

localstorage.html

localstorage.html

144 ms

gtm.js

gtm.js

164 ms

common.js

common.js

115 ms

amzn_ads.js

amzn_ads.js

131 ms

notifications.json

notifications.json

68 ms

global.json

global.json

68 ms

flat.json

flat.json

65 ms

requestHandler

requestHandler

36 ms

liveupdates.js

liveupdates.js

34 ms

ad-view-manager.js

ad-view-manager.js

29 ms

cropped-1.jpg

cropped-1.jpg

89 ms

user.json

user.json

98 ms

bid

bid

90 ms

Accessibility Review

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

High

Links do not have a discernible name

Best Practices

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

globespotters.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 Globespotters.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 Globespotters.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

globespotters.blogs.nytimes.com

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