Tools & Wizards About Us
greeleytribune.net screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

greeleytribune.net

Greeley Tribune - Stay Informed, Stay Connected

Page Load Speed

2.7 sec in total

First Response

185 ms

Resources Loaded

1.8 sec

Page Rendered

783 ms

greeleytribune.net screenshot

About Website

Click here to check amazing Greeley Tribune content. Otherwise, check out these important facts you probably never knew about greeleytribune.net

- Greeley Tribune

Visit greeleytribune.net

Key Findings

We analyzed Greeleytribune.net page load time and found that the first response time was 185 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

greeleytribune.net performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

greeleytribune.net

185 ms

greeleytribune.net

427 ms

style.min.css

163 ms

styles.css

243 ms

widget-areas.min.css

244 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 43% of them (16 requests) were addressed to the original Greeleytribune.net, 24% (9 requests) were made to Fonts.gstatic.com and 16% (6 requests) were made to Blogger.googleusercontent.com. The less responsive or slowest element that took the longest time to load (664 ms) relates to the external source Blogger.googleusercontent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.3 kB (9%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greeleytribune.net main page is 1.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. 45% of websites need less resources to load. Images take 926.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 84.5 kB

  • Original 102.6 kB
  • After minification 100.9 kB
  • After compression 18.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 84.5 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 472 B

  • Original 926.9 kB
  • After minification 926.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. Greeley Tribune images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 5.1 kB

  • Original 50.9 kB
  • After minification 50.9 kB
  • After compression 45.8 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

-19%

Potential reduce by 5.3 kB

  • Original 27.5 kB
  • After minification 27.5 kB
  • After compression 22.3 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. Greeleytribune.net needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (54%)

Requests Now

24

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greeleytribune.net

greeleytribune.net

185 ms

greeleytribune.net

greeleytribune.net

427 ms

style.min.css

style.min.css

163 ms

styles.css

styles.css

243 ms

widget-areas.min.css

widget-areas.min.css

244 ms

main.min.css

main.min.css

245 ms

css

css

36 ms

public.css

public.css

249 ms

style.min.css

style.min.css

256 ms

jquery.min.js

jquery.min.js

430 ms

jquery-migrate.min.js

jquery-migrate.min.js

323 ms

js

js

62 ms

index.js

index.js

323 ms

index.js

index.js

326 ms

menu.min.js

menu.min.js

330 ms

navigation-search.min.js

navigation-search.min.js

341 ms

back-to-top.min.js

back-to-top.min.js

402 ms

Key-takeaways-from-APs-look-at-the-emerging-wave-of.png

Key-takeaways-from-APs-look-at-the-emerging-wave-of.png

264 ms

rock%20hard.jpg

rock%20hard.jpg

312 ms

image_1401237056.jpg

image_1401237056.jpg

284 ms

https%3A%2F%2Fd1e00ek4ebabms.cloudfront.net%2Fproduction%2F7bb8be33-1272-45c1-92b7-5563d2a2878b.jpg

https%3A%2F%2Fd1e00ek4ebabms.cloudfront.net%2Fproduction%2F7bb8be33-1272-45c1-92b7-5563d2a2878b.jpg

201 ms

rome.jpg

rome.jpg

486 ms

Chinese%20blue%20book.jpg

Chinese%20blue%20book.jpg

572 ms

lone%20soldiers.jpg

lone%20soldiers.jpg

524 ms

Erik%20Prince.jpg

Erik%20Prince.jpg

520 ms

Palestinian%20massacres.jpg

Palestinian%20massacres.jpg

664 ms

cropped-cropped-reeley.png

cropped-cropped-reeley.png

135 ms

large.png

large.png

645 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

61 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf

88 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

116 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8Jow.ttf

130 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8Jow.ttf

134 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8Jow.ttf

131 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

130 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8Jow.ttf

133 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8Jow.ttf

133 ms

Accessibility Review

greeleytribune.net accessibility score

95

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

Links do not have a discernible name

Best Practices

greeleytribune.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

greeleytribune.net 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

Links do not have descriptive text

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greeleytribune.net 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), while the claimed language is English. Our system also found out that Greeleytribune.net 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

greeleytribune.net

Open Graph data is detected on the main page of Greeley Tribune. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: