Tools & Wizards About Us
ephall.org screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

ephall.org

Elizabeth Peratrovich Hall (EPH) | Conference Hall & Meeting Rooms | Juneau, AK

Page Load Speed

5.7 sec in total

First Response

233 ms

Resources Loaded

4.9 sec

Page Rendered

594 ms

ephall.org screenshot

About Website

Visit ephall.org now to see the best up-to-date Ep Hall content and also check out these interesting facts you probably never knew about ephall.org

The Elizabeth Peratrovich Hall (EPH) offers a conference hall and meeting rooms in the heart of downtown Juneau, Alaska.

Visit ephall.org

Key Findings

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

ephall.org performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.146

77/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

ephall.org

233 ms

ephall.org

3022 ms

analytics.js

24 ms

sbc.css

254 ms

styles.css

357 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 91% of them (48 requests) were addressed to the original Ephall.org, 6% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Ephall.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 420.9 kB (31%)

Content Size

1.4 MB

After Optimization

940.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ephall.org main page is 1.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 542.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 114.0 kB

  • Original 135.4 kB
  • After minification 132.3 kB
  • After compression 21.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. 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 114.0 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 423 B

  • Original 542.0 kB
  • After minification 541.5 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. Ep Hall images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 198.0 kB

  • Original 423.5 kB
  • After minification 423.5 kB
  • After compression 225.5 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 198.0 kB or 47% of the original size.

CSS Optimization

-42%

Potential reduce by 108.5 kB

  • Original 260.2 kB
  • After minification 260.2 kB
  • After compression 151.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. Ephall.org needs all CSS files to be minified and compressed as it can save up to 108.5 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (72%)

Requests Now

43

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ephall.org

ephall.org

233 ms

ephall.org

ephall.org

3022 ms

analytics.js

analytics.js

24 ms

sbc.css

sbc.css

254 ms

styles.css

styles.css

357 ms

frontend.min.css

frontend.min.css

258 ms

rgs.css

rgs.css

257 ms

font-awesome.min.css

font-awesome.min.css

259 ms

style.css

style.css

466 ms

magnific.css

magnific.css

277 ms

responsive.css

responsive.css

409 ms

nectar-slider.css

nectar-slider.css

295 ms

js_composer.min.css

js_composer.min.css

304 ms

jquery.js

jquery.js

356 ms

jquery-migrate.min.js

jquery-migrate.min.js

357 ms

sbc.js

sbc.js

369 ms

frontend.min.js

frontend.min.js

421 ms

linkid.js

linkid.js

10 ms

collect

collect

14 ms

collect

collect

86 ms

js

js

128 ms

core.min.js

core.min.js

313 ms

widget.min.js

widget.min.js

311 ms

position.min.js

position.min.js

325 ms

menu.min.js

menu.min.js

632 ms

wp-a11y.min.js

wp-a11y.min.js

632 ms

autocomplete.min.js

autocomplete.min.js

632 ms

wpss-search-suggest.js

wpss-search-suggest.js

632 ms

scripts.js

scripts.js

633 ms

modernizr.js

modernizr.js

634 ms

magnific.js

magnific.js

635 ms

superfish.js

superfish.js

634 ms

init.js

init.js

648 ms

nectar-slider.js

nectar-slider.js

637 ms

touchswipe.min.js

touchswipe.min.js

635 ms

wp-embed.min.js

wp-embed.min.js

635 ms

js_composer_front.min.js

js_composer_front.min.js

630 ms

1.png

1.png

95 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

270 ms

OpenSans-Light-webfont.woff

OpenSans-Light-webfont.woff

269 ms

OpenSans-Semibold-webfont.woff

OpenSans-Semibold-webfont.woff

269 ms

OpenSansBold-webfont.woff

OpenSansBold-webfont.woff

271 ms

Lovelo_Black.woff

Lovelo_Black.woff

267 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

269 ms

steadysets.ttf

steadysets.ttf

269 ms

icomoon.woff

icomoon.woff

268 ms

diagonal_line.png

diagonal_line.png

133 ms

slide-1980x735-conference.jpg

slide-1980x735-conference.jpg

93 ms

slide-1980x735-meeting.jpg

slide-1980x735-meeting.jpg

68 ms

slide-1980x735-decorations.jpg

slide-1980x735-decorations.jpg

186 ms

slide-1980%C3%97735-building-2016.jpg

slide-1980%C3%97735-building-2016.jpg

180 ms

ephall.org

ephall.org

279 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

81 ms

Accessibility Review

ephall.org accessibility score

80

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

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

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

ephall.org SEO score

84

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

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

ephall.org

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