Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

aaf.org

American Advertising Federation | Home

Page Load Speed

4.7 sec in total

First Response

721 ms

Resources Loaded

1.8 sec

Page Rendered

2.1 sec

aaf.org screenshot

About Website

Click here to check amazing Aaf content for United States. Otherwise, check out these important facts you probably never knew about aaf.org

Visit aaf.org

Key Findings

We analyzed Aaf.org page load time and found that the first response time was 721 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

aaf.org performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value51.3 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value33.1 s

0/100

10%

Network Requests Diagram

aaf.org

721 ms

node.css

66 ms

defaults.css

75 ms

system.css

77 ms

system-menus.css

95 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 99% of them (84 requests) were addressed to the original Aaf.org, 1% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (721 ms) belongs to the original domain Aaf.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 424.8 kB (21%)

Content Size

2.0 MB

After Optimization

1.6 MB

In fact, the total size of Aaf.org main page is 2.0 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 21.7 kB

  • Original 28.0 kB
  • After minification 24.7 kB
  • After compression 6.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 3.3 kB, which is 12% 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.7 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 45.1 kB

  • Original 1.5 MB
  • After minification 1.5 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. Aaf images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 229.2 kB

  • Original 313.0 kB
  • After minification 257.1 kB
  • After compression 83.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 229.2 kB or 73% of the original size.

CSS Optimization

-82%

Potential reduce by 128.8 kB

  • Original 156.7 kB
  • After minification 122.8 kB
  • After compression 27.9 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. Aaf.org needs all CSS files to be minified and compressed as it can save up to 128.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (70%)

Requests Now

83

After Optimization

25

The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aaf. 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 32 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

aaf.org accessibility score

90

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

Best Practices

aaf.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

aaf.org SEO score

84

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

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

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