4.2 sec in total
1.1 sec
2.1 sec
995 ms
Click here to check amazing Phoenix Rising content for United States. Otherwise, check out these important facts you probably never knew about phoenixrising.me
A Community for People With Myalgic Encephalomyelitis / Chronic Fatigue Syndrome
Visit phoenixrising.meWe analyzed Phoenixrising.me page load time and found that the first response time was 1.1 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
phoenixrising.me performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value3.5 s
63/100
25%
Value3.3 s
90/100
10%
Value20 ms
100/100
30%
Value0.008
100/100
15%
Value4.4 s
83/100
10%
1078 ms
68 ms
68 ms
109 ms
83 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 54% of them (33 requests) were addressed to the original Phoenixrising.me, 13% (8 requests) were made to Apis.google.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Phoenixrising.me.
Page size can be reduced by 239.9 kB (25%)
948.0 kB
708.2 kB
In fact, the total size of Phoenixrising.me main page is 948.0 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. 60% of websites need less resources to load. Images take 667.9 kB which makes up the majority of the site volume.
Potential reduce by 81.7 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 81.7 kB or 79% of the original size.
Potential reduce by 49.8 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. Phoenix Rising images are well optimized though.
Potential reduce by 92.4 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 92.4 kB or 59% of the original size.
Potential reduce by 15.9 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. Phoenixrising.me needs all CSS files to be minified and compressed as it can save up to 15.9 kB or 79% of the original size.
Number of requests can be reduced by 19 (32%)
59
40
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phoenix Rising. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
phoenixrising.me
1078 ms
css.css
68 ms
dcssb.css
68 ms
jquery.js
109 ms
jquery-migrate.min.js
83 ms
ga.social_tracking.js
83 ms
jquery.social.slick.1.0.js
82 ms
widgets.js
109 ms
in.js
7 ms
wp-emoji-release.min.js
95 ms
chillimechallengememe.jpg
151 ms
ga.js
107 ms
pr_wp_logo_max.png
107 ms
pr_wp_logo_max1.png
105 ms
DaveySmith1.jpg
105 ms
Pixabay-watch.jpg
105 ms
professor-james-coyne.jpg
125 ms
Pixabay-petition-signature.jpg
105 ms
IIMEC10.jpg
144 ms
poster-2-278x300.jpg
142 ms
Fluge-and-Mella-300x199.jpg
144 ms
newspapers-444444_640-300x198.jpg
142 ms
capitol-720677_640-300x239.jpg
142 ms
11193297_1598344087114658_1011865320453080262_n.png
148 ms
pixabay-geralt-question-mark-e1433368434929.jpg
200 ms
london-by-night-735085_1280-300x198.jpg
199 ms
pixabay-blue-ribbon.jpg
244 ms
HOPE-MECFS-Facebook-300x200.jpg
199 ms
pixabay-question-silhouettes.jpg
199 ms
DrMadyHornig.jpg
219 ms
wendy-ME-Advocacy-a-e1424740812191.jpg
243 ms
results1-231x300.png
243 ms
Online_Shopping_dk.png
243 ms
social_sprite.png
242 ms
rss.png
254 ms
plusone.js
205 ms
secureAnonymousFramework
133 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
248 ms
__utm.gif
22 ms
__utm.gif
29 ms
like.php
152 ms
share
67 ms
sprite_connect_v14.png
61 ms
cb=gapi.loaded_0
31 ms
cb=gapi.loaded_1
56 ms
fastbutton
100 ms
vpc6VNjRPXV.js
498 ms
LVx-xkvaJ0b.png
561 ms
postmessageRelay
76 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
61 ms
cb=gapi.loaded_0
51 ms
cb=gapi.loaded_1
50 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
101 ms
api.js
38 ms
core:rpc:shindig.random:shindig.sha1.js
85 ms
2536007149-postmessagerelay.js
63 ms
jot
87 ms
fastbutton
66 ms
tab_left_horizontal.png
36 ms
bg_slick_top.png
40 ms
like.php
49 ms
phoenixrising.me accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
phoenixrising.me best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
phoenixrising.me SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phoenixrising.me 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 Phoenixrising.me 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.
phoenixrising.me
Open Graph description is not detected on the main page of Phoenix Rising. 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: