Access tacomaweekly.com. TacomaWeekly

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

tacomaweekly.com

64 ms

tacomaweekly.com

176 ms

bl2.js

179 ms

bootstrap.min.css

71 ms

bootstrap.bundle.min.js

91 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 53% of them (32 requests) were addressed to the original Tacomaweekly.com, 10% (6 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (983 ms) belongs to the original domain Tacomaweekly.com.

Content Size

3.5 MB

After Optimization

3.2 MB

In fact, the total size of Tacomaweekly.com main page is 3.5 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. 55% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 106.3 kB

Original 125.2 kB
After minification 108.5 kB
After compression 18.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 16.7 kB, which is 13% 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 106.3 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 181.1 kB

Original 3.1 MB
After minification 2.9 MB

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. Tacoma Weekly images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 8.7 kB

Original 233.4 kB
After minification 232.4 kB
After compression 224.7 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

-77%

Potential reduce by 36.8 kB

Original 48.0 kB
After minification 35.5 kB
After compression 11.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. Tacomaweekly.com needs all CSS files to be minified and compressed as it can save up to 36.8 kB or 77% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

ARIA IDs are not unique

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

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.

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tacomaweekly.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Tacomaweekly.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

tacomaweekly.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

TacomaWeekly

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

tacomaweekly.com

tacomaweekly.com

bl2.js

bootstrap.min.css

bootstrap.bundle.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

tacomaweekly.com

tacomaweekly.com

bl2.js

bootstrap.min.css

bootstrap.bundle.min.js

bootstrap.css

fancybox.css

normalize.min.css

jquery-1.7.min.js

settings.js

ads.js

menu_horizontal.js

polls.js

articles.js

iframeResizer.min.js

fancybox.umd.js

font-awesome.min.css

jscript1.js

custom.css

custom.js

ufields.css

ufields.js

css2

css2

articlegroup100.js

preview216.js

preview105.js

articlegroup102.js

articlegroup103.js

articlegroup104.js

webfont.js

css

minimize.png

close.png

font

font

font

font

font

font

04-04-2024-06-09-01-am-4414183.png

css2

26-05-2024-05-43-45-pm-6740295.jpeg