2.8 sec in total
74 ms
2.3 sec
428 ms
Click here to check amazing Imbcr content. Otherwise, check out these important facts you probably never knew about imbcr.org
IMBCR is dedicated to advance the treatment of myeloma by connecting possibility through scientific innovation and continuously optimized patient care. A unique and fully integrated research center, i...
Visit imbcr.orgWe analyzed Imbcr.org page load time and found that the first response time was 74 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
imbcr.org performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value22.1 s
0/100
25%
Value11.2 s
5/100
10%
Value3,130 ms
2/100
30%
Value0
100/100
15%
Value22.0 s
1/100
10%
74 ms
166 ms
76 ms
129 ms
68 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Imbcr.org, 74% (78 requests) were made to Imbcr.wpenginepowered.com and 5% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (685 ms) relates to the external source Imbcr.wpenginepowered.com.
Page size can be reduced by 417.0 kB (16%)
2.6 MB
2.2 MB
In fact, the total size of Imbcr.org main page is 2.6 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. 85% 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 1.7 MB which makes up the majority of the site volume.
Potential reduce by 146.2 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 146.2 kB or 82% of the original size.
Potential reduce by 39.2 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. Imbcr images are well optimized though.
Potential reduce by 221.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 221.3 kB or 39% of the original size.
Potential reduce by 10.3 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. Imbcr.org has all CSS files already compressed.
Number of requests can be reduced by 68 (72%)
94
26
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imbcr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
imbcr.org
74 ms
imbcr.org
166 ms
style.min.css
76 ms
magnific-popup.css
129 ms
slick.css
68 ms
wp-igsp-public.css
137 ms
font-awesome.min.css
68 ms
bootstrap-front.css
73 ms
widget-options.css
187 ms
font-awesome.css
82 ms
splide.min.css
88 ms
baguettebox.min.css
96 ms
photonic.min.css
114 ms
tmm_style.css
102 ms
smartslider.min.css
108 ms
css
68 ms
js
80 ms
bootstrap.css
115 ms
working.css
124 ms
css
82 ms
aos.css
121 ms
aos.js
126 ms
n2.min.js
140 ms
smartslider-frontend.min.js
534 ms
ss-simple.min.js
144 ms
w-arrow-image.min.js
138 ms
gravity-forms-theme-reset.min.css
252 ms
gravity-forms-theme-foundation.min.css
128 ms
gravity-forms-theme-framework.min.css
133 ms
flexslider.css
284 ms
public.css
251 ms
public.css
149 ms
formreset.min.css
209 ms
formsmain.min.css
282 ms
readyclass.min.css
251 ms
browsers.min.css
281 ms
jquery.min.js
281 ms
jquery-migrate.min.js
281 ms
accordion-custom.js
473 ms
accordion.js
283 ms
api.js
45 ms
modernizr-2.8.3.min.js
249 ms
bst.js
291 ms
jquery.flexslider.min.js
288 ms
script.min.js
284 ms
wp-polyfill-inert.min.js
335 ms
regenerator-runtime.min.js
331 ms
wp-polyfill.min.js
444 ms
dom-ready.min.js
315 ms
hooks.min.js
394 ms
i18n.min.js
390 ms
a11y.min.js
384 ms
jquery.json.min.js
414 ms
gravityforms.min.js
412 ms
utils.min.js
411 ms
vendor-theme.min.js
375 ms
scripts-theme.min.js
404 ms
akismet-frontend.js
601 ms
mobile-menu.js
592 ms
gtm.js
94 ms
fbevents.js
121 ms
js
82 ms
js
151 ms
destination
184 ms
yF2Fu3g_lGo
333 ms
Berenson_IMBCR_Logo_HOR_POS.svg
127 ms
SliderImg-11.jpg
127 ms
giv-tuesday-banner-3.jpg
149 ms
Family_2-scaled.jpeg
480 ms
Wood_background_3.jpg
150 ms
Precision-Myeloma-Initiatives.jpg
150 ms
Corporte-Match.jpg
176 ms
you-have-WHAT.png
479 ms
i-have-WHAT_RIGHT-TILTED.png
481 ms
eVENTBG.jpg
183 ms
liveyourbestbest.png
321 ms
Home_Slider_3-scaled-1920x500.jpg
330 ms
Event_Header_Dec20_v2.jpg
322 ms
Home_pg_header.jpg
326 ms
Home_What-do-patients.jpg
327 ms
icon_focus_reverse.png
328 ms
icon_care_reverse.png
329 ms
icon_freedom_reverse.png
657 ms
Berenson_IMBCR_Logo_HOR_NEG.svg
329 ms
de1fd37f-b970-4176-ac4f-1894999cea5e.woff
564 ms
3bf6a125-4948-46d6-b44a-25a39c5e1781.woff
563 ms
81a7ca0e-9ecd-494c-b5a8-8a71dee13b8d.woff
539 ms
313088e6-479e-460d-bd11-697e2c96703d.woff
563 ms
KFOmCnqEu92Fr1Mu4mxM.woff
54 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
54 ms
fontawesome-webfont.woff
685 ms
fontawesome-webfont.woff
683 ms
www-player.css
311 ms
www-embed-player.js
336 ms
base.js
340 ms
insight.min.js
191 ms
ad_status.js
334 ms
insight.old.min.js
152 ms
QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js
89 ms
embed.js
42 ms
id
148 ms
KFOmCnqEu92Fr1Mu4mxM.woff
146 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
156 ms
insight_tag_errors.gif
237 ms
Create
30 ms
GenerateIT
14 ms
imbcr.org accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
imbcr.org 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
Page has valid source maps
imbcr.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imbcr.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Imbcr.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.
imbcr.org
Open Graph data is detected on the main page of Imbcr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: