Tools & Wizards About Us
usgbc-mogateway.org screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

usgbc-mogateway.org

Missouri Gateway Green Building Council | Connecting people, places, and planet

Page Load Speed

4.3 sec in total

First Response

116 ms

Resources Loaded

3.1 sec

Page Rendered

1.1 sec

usgbc-mogateway.org screenshot

About Website

Visit usgbc-mogateway.org now to see the best up-to-date Usgbcmo Gateway content for United States and also check out these interesting facts you probably never knew about usgbc-mogateway.org

Visit usgbc-mogateway.org

Key Findings

We analyzed Usgbc-mogateway.org page load time and found that the first response time was 116 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

usgbc-mogateway.org performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.374

28/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

usgbc-mogateway.org

116 ms

www.mogreenbuildings.org

1908 ms

tribe-events-pro-mini-calendar-block.min.css

57 ms

style.min.css

185 ms

style.css

160 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Usgbc-mogateway.org, 83% (74 requests) were made to Mogreenbuildings.org and 10% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Mogreenbuildings.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 770.8 kB (43%)

Content Size

1.8 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Usgbc-mogateway.org main page is 1.8 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 804.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 330.9 kB

  • Original 387.0 kB
  • After minification 381.0 kB
  • After compression 56.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 330.9 kB or 86% of the original size.

Image Optimization

-54%

Potential reduce by 433.1 kB

  • Original 804.4 kB
  • After minification 371.3 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. Obviously, Usgbcmo Gateway needs image optimization as it can save up to 433.1 kB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 5.0 kB

  • Original 550.6 kB
  • After minification 550.1 kB
  • After compression 545.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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 1.8 kB

  • Original 48.5 kB
  • After minification 48.5 kB
  • After compression 46.7 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. Usgbc-mogateway.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 62 (82%)

Requests Now

76

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

usgbc-mogateway.org

usgbc-mogateway.org

116 ms

www.mogreenbuildings.org

www.mogreenbuildings.org

1908 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

57 ms

style.min.css

style.min.css

185 ms

style.css

style.css

160 ms

a11y-toolbar.css

a11y-toolbar.css

163 ms

a11y.css

a11y.css

161 ms

a11y-fontsize.css

a11y-fontsize.css

161 ms

wpa-style.css

wpa-style.css

166 ms

front.min.css

front.min.css

214 ms

wpforms-full.min.css

wpforms-full.min.css

215 ms

style.min.css

style.min.css

210 ms

css

css

34 ms

ie-compat.min.js

ie-compat.min.js

206 ms

et-core-unified-12.min.css

et-core-unified-12.min.css

218 ms

js

js

61 ms

variables-skeleton.min.css

variables-skeleton.min.css

311 ms

common-skeleton.min.css

common-skeleton.min.css

324 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

325 ms

variables-full.min.css

variables-full.min.css

325 ms

common-full.min.css

common-full.min.css

323 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

324 ms

archives.min.css

archives.min.css

324 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

371 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

369 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

369 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

371 ms

jquery.min.js

jquery.min.js

372 ms

jquery-migrate.min.js

jquery-migrate.min.js

370 ms

ctct-plugin-recaptcha-v2.min.js

ctct-plugin-recaptcha-v2.min.js

422 ms

api.js

api.js

33 ms

ctct-plugin-frontend.min.js

ctct-plugin-frontend.min.js

421 ms

wpa-toolbar.js

wpa-toolbar.js

425 ms

a11y.js

a11y.js

425 ms

front.min.js

front.min.js

426 ms

scripts.min.js

scripts.min.js

487 ms

jquery.fitvids.js

jquery.fitvids.js

476 ms

jquery.mobile.js

jquery.mobile.js

477 ms

easypiechart.js

easypiechart.js

480 ms

salvattore.js

salvattore.js

485 ms

frontend-bundle.min.js

frontend-bundle.min.js

485 ms

common.js

common.js

491 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

388 ms

wp-accessibility.js

wp-accessibility.js

394 ms

longdesc.button.js

longdesc.button.js

394 ms

tribe-common.min.js

tribe-common.min.js

396 ms

query-string.min.js

query-string.min.js

391 ms

underscore-before.js

underscore-before.js

414 ms

underscore.min.js

underscore.min.js

389 ms

underscore-after.js

underscore-after.js

397 ms

manager.min.js

manager.min.js

396 ms

gtm.js

gtm.js

100 ms

breakpoints.min.js

breakpoints.min.js

388 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

372 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

82 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

92 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

102 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

102 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

101 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

103 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

102 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

100 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

117 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

336 ms

et-divi-dynamic-tb-706-tb-29-12-late.css

et-divi-dynamic-tb-706-tb-29-12-late.css

324 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

380 ms

swiper-bundle.min.js

swiper-bundle.min.js

381 ms

frontend.min.js

frontend.min.js

381 ms

sticky-elements.js

sticky-elements.js

421 ms

jquery.validate.min.js

jquery.validate.min.js

419 ms

mailcheck.min.js

mailcheck.min.js

336 ms

punycode.min.js

punycode.min.js

375 ms

utils.min.js

utils.min.js

373 ms

wpforms.min.js

wpforms.min.js

373 ms

modules.woff

modules.woff

455 ms

blue-background-with-logo-scaled.jpg

blue-background-with-logo-scaled.jpg

451 ms

solid-backgrounds-lines-scaled.jpg

solid-backgrounds-lines-scaled.jpg

402 ms

ameren.jpg

ameren.jpg

402 ms

mo-history.png

mo-history.png

399 ms

WAKF-1.jpg

WAKF-1.jpg

398 ms

SMART-1.jpg

SMART-1.jpg

466 ms

wash-u.png

wash-u.png

477 ms

spire.png

spire.png

414 ms

reliable.png

reliable.png

472 ms

mobot.png

mobot.png

407 ms

alberici.png

alberici.png

408 ms

recaptcha__en.js

recaptcha__en.js

81 ms

a11y.woff

a11y.woff

159 ms

logo_fullmark.png

logo_fullmark.png

186 ms

Accessibility Review

usgbc-mogateway.org accessibility score

81

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

usgbc-mogateway.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

usgbc-mogateway.org SEO score

83

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 Usgbc-mogateway.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 Usgbc-mogateway.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

usgbc-mogateway.org

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