Tools & Wizards About Us
yakimaherald.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

yakimaherald.com

Yakima Herald-Republic | Yakima, Washington - We Tell Your Stories

Page Load Speed

3.6 sec in total

First Response

75 ms

Resources Loaded

2.9 sec

Page Rendered

648 ms

yakimaherald.com screenshot

About Website

Visit yakimaherald.com now to see the best up-to-date Yakima Herald content for United States and also check out these interesting facts you probably never knew about yakimaherald.com

We help you stay informed on the topics that matter to you.

Visit yakimaherald.com

Key Findings

We analyzed Yakimaherald.com page load time and found that the first response time was 75 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

yakimaherald.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value5,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.062

97/100

15%

TTI (Time to Interactive)

Value34.3 s

0/100

10%

Network Requests Diagram

yakimaherald.com

75 ms

www.yakimaherald.com

105 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

132 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

125 ms

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

146 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 13% of them (18 requests) were addressed to the original Yakimaherald.com, 23% (31 requests) were made to Bloximages.newyork1.vip.townnews.com and 13% (18 requests) were made to Cdn59755463.blazingcdn.net. The less responsive or slowest element that took the longest time to load (458 ms) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 913.5 kB (29%)

Content Size

3.1 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yakimaherald.com main page is 3.1 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. Only a small number of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 545.4 kB

  • Original 617.4 kB
  • After minification 551.4 kB
  • After compression 71.9 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 66.0 kB, which is 11% 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 545.4 kB or 88% of the original size.

Image Optimization

-11%

Potential reduce by 114.7 kB

  • Original 1.1 MB
  • After minification 972.4 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. Obviously, Yakima Herald needs image optimization as it can save up to 114.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-18%

Potential reduce by 235.7 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.1 MB

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 235.7 kB or 18% of the original size.

CSS Optimization

-16%

Potential reduce by 17.7 kB

  • Original 109.2 kB
  • After minification 109.2 kB
  • After compression 91.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. Yakimaherald.com needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (68%)

Requests Now

100

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yakimaherald.com

yakimaherald.com

75 ms

www.yakimaherald.com

www.yakimaherald.com

105 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

132 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

125 ms

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

146 ms

site.css

site.css

144 ms

css

css

112 ms

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

139 ms

flex-utility-text-promo.945a2efac4892ce469180c513f411107.css

flex-utility-text-promo.945a2efac4892ce469180c513f411107.css

146 ms

flex-utility-web-notification-promo.0b74d774b4cb1e043077358dde55f2c8.css

flex-utility-web-notification-promo.0b74d774b4cb1e043077358dde55f2c8.css

150 ms

access.d7adebba498598b0ec2c.js

access.d7adebba498598b0ec2c.js

69 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

153 ms

user.js

user.js

109 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

168 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

174 ms

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

167 ms

application.3c64d611e594b45dd35b935162e79d85.js

application.3c64d611e594b45dd35b935162e79d85.js

175 ms

polyfill.min.js

polyfill.min.js

458 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

174 ms

tnt.dynamic.navigation.2c31f97f685c80e6b8dde49bcd628fd6.js

tnt.dynamic.navigation.2c31f97f685c80e6b8dde49bcd628fd6.js

181 ms

op.js

op.js

131 ms

gpt.js

gpt.js

187 ms

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

174 ms

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

179 ms

firebase-app.js

firebase-app.js

136 ms

firebase-messaging.js

firebase-messaging.js

141 ms

messaging.js

messaging.js

130 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

178 ms

tracking.js

tracking.js

135 ms

fontawesome.568f3d1ab17b33ce05854081baadadac.js

fontawesome.568f3d1ab17b33ce05854081baadadac.js

179 ms

flipptag.js

flipptag.js

135 ms

load_tags.js

load_tags.js

139 ms

loader.min.js

loader.min.js

112 ms

index.min.js

index.min.js

139 ms

load.js

load.js

316 ms

tracker.js

tracker.js

136 ms

classic-071822.css

classic-071822.css

134 ms

mc-validate.js

mc-validate.js

167 ms

get.js

get.js

131 ms

tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js

tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js

166 ms

web_promo_popup.14c8c9be316ddae42fed9ffd17243231.js

web_promo_popup.14c8c9be316ddae42fed9ffd17243231.js

166 ms

tnt.regions.b44801b45845a81b995eeaad12f4f276.js

tnt.regions.b44801b45845a81b995eeaad12f4f276.js

182 ms

index.min.js

index.min.js

36 ms

gtm.js

gtm.js

49 ms

gtm.js

gtm.js

91 ms

analytics.js

analytics.js

92 ms

gtm.js

gtm.js

63 ms

gtm.js

gtm.js

105 ms

publisher:getClientId

publisher:getClientId

128 ms

destination

destination

114 ms

gtm.js

gtm.js

185 ms

gtm.js

gtm.js

183 ms

prum.min.js

prum.min.js

188 ms

polyfill.min.js

polyfill.min.js

394 ms

a8d3897e-6f2d-11ec-a31e-5b54629cf7c0.png

a8d3897e-6f2d-11ec-a31e-5b54629cf7c0.png

174 ms

get_image.aspx

get_image.aspx

330 ms

173 ms

99c01d1c-6f2d-11ec-a31e-6b664fb99a7b.png

99c01d1c-6f2d-11ec-a31e-6b664fb99a7b.png

172 ms

a1e59170-6f2d-11ec-a31e-432b85925fcb.png

a1e59170-6f2d-11ec-a31e-432b85925fcb.png

171 ms

171 ms

171 ms

171 ms

171 ms

177 ms

175 ms

%7B%7Bimage%7D%7D

%7B%7Bimage%7D%7D

177 ms

collect

collect

164 ms

collect

collect

401 ms

pubads_impl.js

pubads_impl.js

123 ms

tracker.gif

tracker.gif

116 ms

63c078e15a884.image.jpg

63c078e15a884.image.jpg

224 ms

63c078a963a01.image.jpg

63c078a963a01.image.jpg

223 ms

63c0793ea7b91.image.jpg

63c0793ea7b91.image.jpg

222 ms

63c0789cd13f9.image.jpg

63c0789cd13f9.image.jpg

223 ms

63c078e9aaf36.image.jpg

63c078e9aaf36.image.jpg

218 ms

63c078b320b72.image.jpg

63c078b320b72.image.jpg

219 ms

63c078ff89a72.image.jpg

63c078ff89a72.image.jpg

241 ms

212 ms

analytics.min.js

analytics.min.js

275 ms

js

js

107 ms

js

js

93 ms

81279359

81279359

440 ms

va9E4kDNxMZdWfMOD5Vvl4jNazX3dA.woff

va9E4kDNxMZdWfMOD5Vvl4jNazX3dA.woff

409 ms

loader-config.json

loader-config.json

384 ms

settings

settings

24 ms

ai.0.js

ai.0.js

128 ms

fp.min.js

fp.min.js

232 ms

g2i.min.js

g2i.min.js

232 ms

t8y9347t.min.js

t8y9347t.min.js

152 ms

t8y9347t.min.css

t8y9347t.min.css

230 ms

870.bundle.6e2976b75e60ab2b2bf8.js

870.bundle.6e2976b75e60ab2b2bf8.js

94 ms

tsub-middleware.bundle.77315eced46c5ae4c052.js

tsub-middleware.bundle.77315eced46c5ae4c052.js

105 ms

AGSKWxX0TJLQTBDmomK7dGPNmb25izAeKFkIhiMxaviS3oWgsNSxSdOyRW2KWgpLhMaYcaCN4C-GtPcCQ0mfrgmXy3H3gYJRyABjZWWME8PcneRb0Vkm_zY_867z9Lxo0Z8t7fRMPaWorw==

AGSKWxX0TJLQTBDmomK7dGPNmb25izAeKFkIhiMxaviS3oWgsNSxSdOyRW2KWgpLhMaYcaCN4C-GtPcCQ0mfrgmXy3H3gYJRyABjZWWME8PcneRb0Vkm_zY_867z9Lxo0Z8t7fRMPaWorw==

97 ms

AGSKWxWsOHiMJs_R2snbk3X--INebjwM6UcAVlcC2NyirwmZ6mecslLOtxAuZ7C7ixtzpRpsJpeE33PtVAi5qgQhGTRMJ_sW1gdzig4R_0dvYekR2J-H6_YJ9Uw12FArdxoyCbJsT2eqeQ==

AGSKWxWsOHiMJs_R2snbk3X--INebjwM6UcAVlcC2NyirwmZ6mecslLOtxAuZ7C7ixtzpRpsJpeE33PtVAi5qgQhGTRMJ_sW1gdzig4R_0dvYekR2J-H6_YJ9Uw12FArdxoyCbJsT2eqeQ==

130 ms

m

m

388 ms

gtm.js

gtm.js

43 ms

ad_300_250.jpg

ad_300_250.jpg

82 ms

index.js

index.js

81 ms

YHR__YHRCONFIG.json

YHR__YHRCONFIG.json

36 ms

10567.jsx

10567.jsx

52 ms

self

self

271 ms

WidgetTemplate.min.css

WidgetTemplate.min.css

22 ms

angular.min.js

angular.min.js

45 ms

widgetcombined2.min.js

widgetcombined2.min.js

23 ms

p-uq0GLFySb_d1T.gif

p-uq0GLFySb_d1T.gif

210 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

281 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

282 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

285 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

285 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

285 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

285 ms

icomoon.woff

icomoon.woff

147 ms

kY_YnEoQqEWltxoIXBFaEg.medium.jpg

kY_YnEoQqEWltxoIXBFaEg.medium.jpg

278 ms

ajax-loader.gif

ajax-loader.gif

138 ms

Ucr6U0Z-mUKc2Flo-DTDDQ.medium.jpg

Ucr6U0Z-mUKc2Flo-DTDDQ.medium.jpg

277 ms

5245d79e-4890-4dba-8b48-8a1090c252b9.medium.png

5245d79e-4890-4dba-8b48-8a1090c252b9.medium.png

432 ms

_23ao08W6ECMQf3fYShoIg.medium.png

_23ao08W6ECMQf3fYShoIg.medium.png

440 ms

ae93f32a-2df3-4977-9ef2-1a0421a913da.medium.png

ae93f32a-2df3-4977-9ef2-1a0421a913da.medium.png

441 ms

bcf698a6-0109-4ebc-a7ec-cfd1fc436bab.medium.png

bcf698a6-0109-4ebc-a7ec-cfd1fc436bab.medium.png

440 ms

x4HWxi1QtEOj3g7ERk9tkQ.medium.jpg

x4HWxi1QtEOj3g7ERk9tkQ.medium.jpg

440 ms

ncS7W9bP_k6JPoDJOc6XFQ.medium.jpg

ncS7W9bP_k6JPoDJOc6XFQ.medium.jpg

440 ms

SjgE-TsURUSntoBegEJggA.medium.jpg

SjgE-TsURUSntoBegEJggA.medium.jpg

440 ms

oHkXVwWL7UGnxAgmLAGKbw.medium.png

oHkXVwWL7UGnxAgmLAGKbw.medium.png

442 ms

b2bc5f47-e2b6-4ff5-9bd5-6aed26198877.medium.png

b2bc5f47-e2b6-4ff5-9bd5-6aed26198877.medium.png

443 ms

IHsB_xpvAUq7mr5xMPbLOQ.medium.jpg

IHsB_xpvAUq7mr5xMPbLOQ.medium.jpg

441 ms

hNJdMO31F02z8dYYbhsGHQ.medium.jpg

hNJdMO31F02z8dYYbhsGHQ.medium.jpg

445 ms

cKwJ2SzF20yEvkccdTr94w.medium.jpg

cKwJ2SzF20yEvkccdTr94w.medium.jpg

441 ms

a62436bf-e579-4941-88c6-c0b4e66bb77c.medium.png

a62436bf-e579-4941-88c6-c0b4e66bb77c.medium.png

446 ms

5RmQ_xOlwUOtRjXfH8Upjg.medium.jpg

5RmQ_xOlwUOtRjXfH8Upjg.medium.jpg

444 ms

5d74ea44-09c3-4879-b061-63407a1ccca0.medium.png

5d74ea44-09c3-4879-b061-63407a1ccca0.medium.png

443 ms

WBRDRFwL-EqEdhWZ7KbyuQ.medium.jpg

WBRDRFwL-EqEdhWZ7KbyuQ.medium.jpg

444 ms

p-uq0GLFySb_d1T.gif

p-uq0GLFySb_d1T.gif

116 ms

12 ms

ml.gz.js

ml.gz.js

6 ms

Accessibility Review

yakimaherald.com accessibility score

77

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-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

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

yakimaherald.com SEO score

77

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

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

yakimaherald.com

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