Tools & Wizards About Us

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fresh100.com

100.3 WNIC - The 80's 'Til Now in Detroit

Page Load Speed

6 sec in total

First Response

1 sec

Resources Loaded

4.3 sec

Page Rendered

706 ms

About Website

Click here to check amazing Fresh 100 content. Otherwise, check out these important facts you probably never knew about fresh100.com

Don't miss out on the latest from 100.3 WNIC, The 80's 'Til Now in Detroit

Visit fresh100.com

Key Findings

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

Performance Metrics

fresh100.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value4.1 s

78/100

10%

TBT (Total Blocking Time)

Value1,130 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.104

89/100

15%

TTI (Time to Interactive)

Value8.4 s

38/100

10%

Network Requests Diagram

fresh100.com

1043 ms

wnic.iheart.com

926 ms

analytics.js

52 ms

main-2de973f19e.min.css

71 ms

font-awesome.min.css

29 ms

Our browser made a total of 149 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fresh100.com, 26% (38 requests) were made to I.iheart.com and 6% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Fresh100.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (43%)

Content Size

2.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fresh100.com main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 924.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 393.8 kB

  • Original 451.8 kB
  • After minification 401.4 kB
  • After compression 58.0 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 50.5 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 393.8 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 9.2 kB

  • Original 924.4 kB
  • After minification 915.2 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. Fresh 100 images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 407.3 kB

  • Original 754.6 kB
  • After minification 735.2 kB
  • After compression 347.3 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 407.3 kB or 54% of the original size.

CSS Optimization

-76%

Potential reduce by 242.7 kB

  • Original 321.4 kB
  • After minification 319.7 kB
  • After compression 78.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. Fresh100.com needs all CSS files to be minified and compressed as it can save up to 242.7 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (52%)

Requests Now

121

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

fresh100.com accessibility score

89

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

SEO Factors

fresh100.com SEO score

92

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fresh100.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fresh100.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

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