4.1 sec in total
812 ms
3 sec
284 ms
Click here to check amazing Why AmI Still Sick content. Otherwise, check out these important facts you probably never knew about whyamistillsick.com
This film leverages interviews from top clinical experts with patients affected by bacterial biofilms to reach as wide an audience as possible.
Visit whyamistillsick.comWe analyzed Whyamistillsick.com page load time and found that the first response time was 812 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
whyamistillsick.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value10.4 s
0/100
25%
Value10.1 s
9/100
10%
Value2,720 ms
3/100
30%
Value0.326
35/100
15%
Value21.5 s
1/100
10%
812 ms
59 ms
113 ms
157 ms
163 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 69% of them (68 requests) were addressed to the original Whyamistillsick.com, 5% (5 requests) were made to Youtube.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Whyamistillsick.api.oneall.com.
Page size can be reduced by 176.5 kB (9%)
1.9 MB
1.7 MB
In fact, the total size of Whyamistillsick.com main page is 1.9 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. 80% 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 993.0 kB which makes up the majority of the site volume.
Potential reduce by 132.9 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 132.9 kB or 81% of the original size.
Potential reduce by 36.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. Why AmI Still Sick images are well optimized though.
Potential reduce by 6.3 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.
Potential reduce by 565 B
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. Whyamistillsick.com has all CSS files already compressed.
Number of requests can be reduced by 64 (70%)
91
27
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why AmI Still Sick. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
www.whyamistillsick.com
812 ms
dashicons.min.css
59 ms
extra.min.css
113 ms
autoptimize_single_46b21febf02fc29035f608485cb6dade.css
157 ms
style.min.css
163 ms
mediaelementplayer-legacy.min.css
165 ms
wp-mediaelement.min.css
156 ms
autoptimize_single_58be32b1de9286357161bd2936231a4f.css
160 ms
autoptimize_single_a2ac93a7d9c94a52bab46f90b6ff5932.css
166 ms
autoptimize_single_ed67af0cefb999027e3318b11f7a2822.css
209 ms
bbpress.min.css
210 ms
autoptimize_single_8ad748020df131ca6786bf41dd715ceb.css
215 ms
autoptimize_single_279a41fe094a1c0ff59f6d84dc6ec0d2.css
212 ms
autoptimize_single_4b5e90a5a45612fd405ec7d07ff134d0.css
215 ms
css
65 ms
css
84 ms
font-awesome.min.css
219 ms
bootstrap.min.css
269 ms
hover.min.css
264 ms
autoptimize_single_02aa2fc1c18bb68b1268fae5dfe3ef8f.css
268 ms
swiper.min.css
274 ms
autoptimize_single_56bbafa75e85d529a795c2631b043c6f.css
275 ms
autoptimize_single_dc727edb4bc48f77dc6cf3d76b0ee5a2.css
278 ms
autoptimize_single_cedcaab8c4cd6f2c52442f216c7e3043.css
317 ms
autoptimize_single_850e3f4539c87475339570be4c332db6.css
319 ms
social-logos.min.css
321 ms
user-ranking.css
317 ms
jquery-3.7.1.min.js
330 ms
jquery-migrate-3.5.2.min.js
328 ms
dom-ready.min.js
372 ms
base.js
371 ms
script.min.js
373 ms
bbppu.js
374 ms
bbpvotes.js
380 ms
swa.js
385 ms
jquery.blockUI.min.js
427 ms
add-to-cart.min.js
425 ms
js.cookie.min.js
432 ms
s-202445.js
48 ms
js
89 ms
api.js
65 ms
adsbygoogle.js
76 ms
gprofiles.js
44 ms
e-202445.js
47 ms
autoptimize_single_d7a8127861fe37f332ec855349a23c3d.css
425 ms
woocommerce.min.js
382 ms
bp-like.js
333 ms
external.js
337 ms
custom.js
331 ms
wpgroho.js
327 ms
navigation.js
424 ms
skip-link-focus-fix.js
422 ms
sourcebuster.min.js
437 ms
order-attribution.min.js
434 ms
cart-fragments.min.js
433 ms
sharing.min.js
432 ms
library.js
1014 ms
lKcMcQdBk4M
230 ms
da1ee63ec3fd532c358b348c86536016
157 ms
background-8-3.jpg
118 ms
2000px-Paranasal_sinuses_numbers.svg_-600x600.png
218 ms
Tick-Close-up-600x600.jpg
153 ms
Staphylococcus_aureus_AB_Test-600x600.jpg
153 ms
5827340182_5f61c3f09b_b-600x600.jpg
156 ms
Colorful-bugs-600x600.jpg
218 ms
20100905_211652_Spirochetes-600x600.jpg
218 ms
Polymicrobic_biofilm_epifluorescence.jpg
220 ms
number-of-different-microorganisms-including-elongated-diatoms-and-an-amorphic-gelatinous-biofilm-mass-600x600.jpg
301 ms
2000px-Two_chamber_heart.svg_-600x600.png
301 ms
Alcor-OR31-e1299273577259-600x600.jpg
302 ms
Polymicrobic_biofilm_epifluorescence-600x449.jpg
319 ms
external.png
302 ms
WAISS-Poster-21-600x600.jpg
319 ms
2000px-Paranasal_sinuses_numbers.svg_-150x150.png
319 ms
Tick-Close-up-150x150.jpg
318 ms
Staphylococcus_aureus_AB_Test-150x150.jpg
318 ms
show_ads_impl.js
104 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf
94 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
93 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf
94 ms
fontawesome-webfont.woff
295 ms
www-player.css
64 ms
www-embed-player.js
105 ms
base.js
239 ms
zrt_lookup.html
200 ms
ads
456 ms
count.json
138 ms
g.gif
413 ms
www.whyamistillsick.com
580 ms
ad_status.js
172 ms
V6n6N6lR58V6YvKWzRgNRm2UbnEaYiTpGDY0zZzDx9c.js
107 ms
embed.js
26 ms
ca-pub-4489939496834224
169 ms
id
45 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
44 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
43 ms
Create
193 ms
autoptimize_single_29ed0396622780590223cd919f310dd7.css
121 ms
whyamistillsick.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
whyamistillsick.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
whyamistillsick.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whyamistillsick.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 Whyamistillsick.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.
whyamistillsick.com
Open Graph data is detected on the main page of Why AmI Still Sick. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: