Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

youdontsay.org

"You Don't Say" -- Conservative politics, links, surprises.

Page Load Speed

3.7 sec in total

First Response

44 ms

Resources Loaded

423 ms

Page Rendered

3.2 sec

youdontsay.org screenshot

About Website

Visit youdontsay.org now to see the best up-to-date You Don T Say content and also check out these interesting facts you probably never knew about youdontsay.org

A generous serving of political discourse, loads of useful website links, a heaping helping of humor, and several surprises.

Visit youdontsay.org

Key Findings

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

youdontsay.org performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

youdontsay.org

44 ms

buffer.png

98 ms

diggit.png

94 ms

email.png

94 ms

facebook.png

95 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 61% of them (27 requests) were addressed to the original Youdontsay.org, 32% (14 requests) were made to Simplesharebuttons.com and 2% (1 request) were made to Cdn.clustrmaps.com. The less responsive or slowest element that took the longest time to load (259 ms) relates to the external source Clustrmaps.com.

Page Optimization Overview & Recommendations

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

Content Size

2.6 MB

After Optimization

2.3 MB

In fact, the total size of Youdontsay.org main page is 2.6 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. 75% 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 180.7 kB

  • Original 245.5 kB
  • After minification 219.0 kB
  • After compression 64.8 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 26.4 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 180.7 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 48.1 kB

  • Original 2.3 MB
  • After minification 2.3 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. You Don T Say images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 11 (26%)

Requests Now

42

After Optimization

31

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of You Don T Say. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Accessibility Review

youdontsay.org accessibility score

85

Accessibility Issues

Internationalization and localization

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

Impact

Issue

High

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

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

youdontsay.org best practices score

67

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

SEO Factors

youdontsay.org SEO score

67

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Youdontsay.org 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 Youdontsay.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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