Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

centralexchange.org

Central Exchange

Page Load Speed

4.2 sec in total

First Response

639 ms

Resources Loaded

2.4 sec

Page Rendered

1.2 sec

centralexchange.org screenshot

About Website

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

For over 40 years, Central Exchange has worked to support women and believes that all women should have the opportunity to reach their full potential. When ambitious women receive more opportunity for...

Visit centralexchange.org

Key Findings

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

centralexchange.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

centralexchange.org

639 ms

jquery.min.js

34 ms

bootstrap.min.css

20 ms

bootstrap.min.js

19 ms

css

28 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 16% of them (16 requests) were addressed to the original Centralexchange.org, 23% (24 requests) were made to 96bda424cfcc34d9dd1a-0a7f10f87519dba22d2dbc6233a731e5.r41.cf2.rackcdn.com and 11% (11 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source 96bda424cfcc34d9dd1a-0a7f10f87519dba22d2dbc6233a731e5.r41.cf2.rackcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (27%)

Content Size

6.4 MB

After Optimization

4.7 MB

In fact, the total size of Centralexchange.org main page is 6.4 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 4.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 80.4 kB

  • Original 98.5 kB
  • After minification 93.4 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 80.4 kB or 82% of the original size.

Image Optimization

-10%

Potential reduce by 498.0 kB

  • Original 4.8 MB
  • After minification 4.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. Central Exchange images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 691.4 kB

  • Original 938.0 kB
  • After minification 792.5 kB
  • After compression 246.6 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 691.4 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 480.4 kB

  • Original 560.8 kB
  • After minification 477.1 kB
  • After compression 80.4 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. Centralexchange.org needs all CSS files to be minified and compressed as it can save up to 480.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (48%)

Requests Now

98

After Optimization

51

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

Accessibility Review

centralexchange.org accessibility score

82

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

centralexchange.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

centralexchange.org SEO score

79

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Centralexchange.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 Centralexchange.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 Central Exchange. 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: