Tools & Wizards About Us
phoenixpole.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

phoenixpole.com

Studio Phoenix - Studio Phoenix Pole Dancing & Aerial Chicago

Page Load Speed

1.2 sec in total

First Response

156 ms

Resources Loaded

849 ms

Page Rendered

206 ms

phoenixpole.com screenshot

About Website

Visit phoenixpole.com now to see the best up-to-date Phoenix Pole content and also check out these interesting facts you probably never knew about phoenixpole.com

Studio Phoenix Pole Dancing and Aerial Fitness. We provide dance and fitness classes for women of all shapes, sizes and ages!

Visit phoenixpole.com

Key Findings

We analyzed Phoenixpole.com page load time and found that the first response time was 156 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

phoenixpole.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.248

50/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

phoenixpole.com

156 ms

www.phoenixpole.com

217 ms

fbevents.js

36 ms

sites.css

14 ms

fancybox.css

23 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 45% of them (20 requests) were addressed to the original Phoenixpole.com, 48% (21 requests) were made to Cdn2.editmysite.com and 2% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (217 ms) belongs to the original domain Phoenixpole.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.0 kB (13%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phoenixpole.com main page is 2.1 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.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 87.1 kB

  • Original 106.1 kB
  • After minification 104.7 kB
  • After compression 19.0 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 87.1 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 3.6 kB

  • Original 1.3 MB
  • After minification 1.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. Phoenix Pole images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 183.9 kB

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

CSS Optimization

-1%

Potential reduce by 382 B

  • Original 35.6 kB
  • After minification 35.6 kB
  • After compression 35.2 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. Phoenixpole.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (49%)

Requests Now

37

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phoenixpole.com

phoenixpole.com

156 ms

www.phoenixpole.com

www.phoenixpole.com

217 ms

fbevents.js

fbevents.js

36 ms

sites.css

sites.css

14 ms

fancybox.css

fancybox.css

23 ms

main_style.css

main_style.css

109 ms

font.css

font.css

24 ms

font.css

font.css

24 ms

slideshow.css

slideshow.css

31 ms

templateArtifacts.js

templateArtifacts.js

107 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

35 ms

stl.js

stl.js

27 ms

main.js

main.js

58 ms

commerce-core.js

commerce-core.js

26 ms

main-commerce-browse.js

main-commerce-browse.js

30 ms

slideshow-jq.js

slideshow-jq.js

30 ms

stl.js

stl.js

34 ms

email-decode.min.js

email-decode.min.js

21 ms

main-customer-accounts-site.js

main-customer-accounts-site.js

56 ms

8bbhgnvuamiz.js

8bbhgnvuamiz.js

132 ms

ga.js

ga.js

86 ms

snowday262.js

snowday262.js

72 ms

body-bg-orange.jpg

body-bg-orange.jpg

177 ms

social-dark.png

social-dark.png

124 ms

phoenix-logo-white-on-black-websitelarge.png

phoenix-logo-white-on-black-websitelarge.png

39 ms

main-top-bg.png

main-top-bg.png

126 ms

button_orange.png

button_orange.png

141 ms

sample-app-icon.jpg

sample-app-icon.jpg

39 ms

want-to-try-banner-ad-square_2_orig.jpg

want-to-try-banner-ad-square_2_orig.jpg

58 ms

bachelorette-banner-ad-square_2_orig.jpg

bachelorette-banner-ad-square_2_orig.jpg

67 ms

10-reasons-banner_orig.jpg

10-reasons-banner_orig.jpg

83 ms

2023-instructors-group-2dc-small_orig.jpg

2023-instructors-group-2dc-small_orig.jpg

91 ms

full-group-silly-small_orig.jpg

full-group-silly-small_orig.jpg

112 ms

6539275_orig.jpg

6539275_orig.jpg

110 ms

dsc-2291cropsmall_1_orig.jpg

dsc-2291cropsmall_1_orig.jpg

128 ms

tashona-pole-small_1_orig.jpg

tashona-pole-small_1_orig.jpg

136 ms

sally-favs-small-102_orig.jpg

sally-favs-small-102_orig.jpg

164 ms

control_icons.gif

control_icons.gif

23 ms

loading.gif

loading.gif

23 ms

regular.woff

regular.woff

23 ms

regular.woff

regular.woff

23 ms

light.woff

light.woff

23 ms

ultralight.woff

ultralight.woff

22 ms

bold.woff

bold.woff

23 ms

Accessibility Review

phoenixpole.com accessibility score

82

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

Image elements do not have [alt] attributes

Best Practices

phoenixpole.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

phoenixpole.com SEO score

77

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

High

Image elements do not have [alt] attributes

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

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 Phoenixpole.com 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 Phoenixpole.com 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

phoenixpole.com

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