Tools & Wizards About Us
weft.org screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

weft.org

WEFT

Page Load Speed

2.8 sec in total

First Response

272 ms

Resources Loaded

2 sec

Page Rendered

622 ms

weft.org screenshot

About Website

Welcome to weft.org homepage info - get ready to check WEFT best content for United States right away, or after learning these important things about weft.org

Community radio based in Champaign-Urbana, Illinois since 1981.

Visit weft.org

Key Findings

We analyzed Weft.org page load time and found that the first response time was 272 ms and then it took 2.6 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

weft.org performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

weft.org

272 ms

new.weft.org

266 ms

css

21 ms

style.css

153 ms

now-playing-v2

100 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Weft.org, 48% (15 requests) were made to New.weft.org and 16% (5 requests) were made to Spinitron.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Is3-ssl.mzstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 342.0 kB (11%)

Content Size

3.1 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weft.org 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. 35% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 21.1 kB

  • Original 28.4 kB
  • After minification 20.5 kB
  • After compression 7.3 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 7.9 kB, which is 28% 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 21.1 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 134.9 kB

  • Original 2.8 MB
  • After minification 2.7 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. WEFT images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 181.0 kB

  • Original 244.5 kB
  • After minification 244.5 kB
  • After compression 63.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 181.0 kB or 74% of the original size.

CSS Optimization

-40%

Potential reduce by 5.0 kB

  • Original 12.6 kB
  • After minification 12.5 kB
  • After compression 7.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. Weft.org needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 40% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WEFT. According to our analytics all requests are already optimized.

Network Requests Diagram

weft.org

weft.org

272 ms

new.weft.org

new.weft.org

266 ms

css

css

21 ms

style.css

style.css

153 ms

now-playing-v2

now-playing-v2

100 ms

HMA_24.png

HMA_24.png

454 ms

WEFT_logo_rainbow.jpg

WEFT_logo_rainbow.jpg

323 ms

listen_live.jpg

listen_live.jpg

158 ms

Donate-Now-Lt-Blue.jpg

Donate-Now-Lt-Blue.jpg

158 ms

Rotational_2024_May.jpg

Rotational_2024_May.jpg

385 ms

WEFT-fest23_v1.jpg

WEFT-fest23_v1.jpg

527 ms

Turf_Club_Floor_Plan.jpg

Turf_Club_Floor_Plan.jpg

609 ms

Spinitron_Ark_Calendar_medium.jpg

Spinitron_Ark_Calendar_medium.jpg

465 ms

spark_player.jpg

spark_player.jpg

383 ms

Antenna_Video_promo.jpg

Antenna_Video_promo.jpg

536 ms

nowPlaying.min.css

nowPlaying.min.css

97 ms

170x170bb.jpg

170x170bb.jpg

113 ms

150x150bb.jpg

150x150bb.jpg

32 ms

170x170bb.jpg

170x170bb.jpg

32 ms

musickit.js

musickit.js

62 ms

nowPlaying.min.js

nowPlaying.min.js

131 ms

170x170bb.jpg

170x170bb.jpg

1317 ms

170x170bb.jpg

170x170bb.jpg

118 ms

piwik.js

piwik.js

304 ms

musickit.js

musickit.js

16 ms

apple.png

apple.png

16 ms

amazon.png

amazon.png

28 ms

spotify.png

spotify.png

129 ms

font

font

53 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

207 ms

piwik.php

piwik.php

152 ms

Accessibility Review

weft.org accessibility score

76

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

weft.org 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

weft.org SEO score

87

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weft.org 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 Weft.org 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

weft.org

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