Tools & Wizards About Us
aplex.org screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

aplex.org

The Aplex | Event Center in Alpena MI

Page Load Speed

2.4 sec in total

First Response

143 ms

Resources Loaded

2.1 sec

Page Rendered

81 ms

aplex.org screenshot

About Website

Click here to check amazing Aplex content. Otherwise, check out these important facts you probably never knew about aplex.org

The APlex is Alpena's premier event center. We host anything from weddings, to live entertainment and sports. We look forward to having you!

Visit aplex.org

Key Findings

We analyzed Aplex.org page load time and found that the first response time was 143 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

aplex.org performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.052

98/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

www.aplex.org

143 ms

minified.js

47 ms

focus-within-polyfill.js

45 ms

polyfill.min.js

1000 ms

thunderbolt-commons.e7839053.bundle.min.js

83 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Aplex.org, 33% (15 requests) were made to Static.parastorage.com and 31% (14 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1000 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.9 kB (28%)

Content Size

908.2 kB

After Optimization

653.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Aplex.org main page is 908.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 342.4 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 249.6 kB

  • Original 342.4 kB
  • After minification 340.6 kB
  • After compression 92.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. 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 249.6 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 305.5 kB
  • After minification 304.4 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. Aplex images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.2 kB

  • Original 260.4 kB
  • After minification 260.3 kB
  • After compression 256.1 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.

Requests Breakdown

Number of requests can be reduced by 10 (34%)

Requests Now

29

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.aplex.org

www.aplex.org

143 ms

minified.js

minified.js

47 ms

focus-within-polyfill.js

focus-within-polyfill.js

45 ms

polyfill.min.js

polyfill.min.js

1000 ms

thunderbolt-commons.e7839053.bundle.min.js

thunderbolt-commons.e7839053.bundle.min.js

83 ms

main.760485a2.bundle.min.js

main.760485a2.bundle.min.js

85 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

76 ms

lodash.min.js

lodash.min.js

82 ms

react.production.min.js

react.production.min.js

81 ms

react-dom.production.min.js

react-dom.production.min.js

83 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

81 ms

5e8aa3_bb0418f333f744afad452b9ac45c8840~mv2_d_4016_6016_s_4_2.jpg

5e8aa3_bb0418f333f744afad452b9ac45c8840~mv2_d_4016_6016_s_4_2.jpg

373 ms

aplex1.jpg

aplex1.jpg

322 ms

5e8aa3_f6887d2c25604cc7b92ee13cba1f3459.jpg

5e8aa3_f6887d2c25604cc7b92ee13cba1f3459.jpg

345 ms

5e8aa3_e9c2dc90ff674509bca337db413d8fb7.jpg

5e8aa3_e9c2dc90ff674509bca337db413d8fb7.jpg

350 ms

5e8aa3_d1a22a3593064fb082b2e2a6a14a1101.jpg

5e8aa3_d1a22a3593064fb082b2e2a6a14a1101.jpg

389 ms

Diamond%20Rio%20Partners%20Poster%20Final.png

Diamond%20Rio%20Partners%20Poster%20Final.png

329 ms

1392718_316139345191164_993617698_n.jpg

1392718_316139345191164_993617698_n.jpg

568 ms

5e8aa3_438082d5847149c0bed64f41cb969ad9.jpg

5e8aa3_438082d5847149c0bed64f41cb969ad9.jpg

530 ms

214ec6_f9fcea12bd9539ab78997f1eb2c141ba.png

214ec6_f9fcea12bd9539ab78997f1eb2c141ba.png

528 ms

214ec6_1b0bff64b32a82934bd57192dd391250.png

214ec6_1b0bff64b32a82934bd57192dd391250.png

555 ms

214ec6_3b0aec10ae31552353f591a4b5748e31.png

214ec6_3b0aec10ae31552353f591a4b5748e31.png

373 ms

214ec6_1b0bff64b32a82934bd57192dd391250.png

214ec6_1b0bff64b32a82934bd57192dd391250.png

458 ms

5e8aa3_9fc6309f8f33450aa98613a72b9182e7.jpg

5e8aa3_9fc6309f8f33450aa98613a72b9182e7.jpg

600 ms

IMG_3641.jpg

IMG_3641.jpg

659 ms

bundle.min.js

bundle.min.js

59 ms

98 ms

96 ms

95 ms

95 ms

94 ms

92 ms

129 ms

129 ms

128 ms

126 ms

126 ms

122 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

24 ms

deprecation-style.v5.css

deprecation-style.v5.css

9 ms

right-arrow.svg

right-arrow.svg

15 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

6 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

6 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

Accessibility Review

aplex.org accessibility score

91

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

Best Practices

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

aplex.org SEO score

91

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

aplex.org

Open Graph data is detected on the main page of Aplex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: