2.2 sec in total
408 ms
1.4 sec
362 ms
Visit janssen.com.mx now to see the best up-to-date Janssen content and also check out these interesting facts you probably never knew about janssen.com.mx
Explore Janssen’s innovative medical research & pharmaceutical product development practices to see how Janssen is creating a future where disease is a thing of the past.
Visit janssen.com.mxWe analyzed Janssen.com.mx page load time and found that the first response time was 408 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
janssen.com.mx performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value13.0 s
0/100
25%
Value6.0 s
46/100
10%
Value610 ms
49/100
30%
Value1.104
1/100
15%
Value9.7 s
28/100
10%
408 ms
114 ms
34 ms
63 ms
67 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Janssen.com.mx, 93% (118 requests) were made to Janssen.com and 2% (3 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (408 ms) belongs to the original domain Janssen.com.mx.
Page size can be reduced by 385.3 kB (23%)
1.7 MB
1.3 MB
In fact, the total size of Janssen.com.mx main page is 1.7 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. 75% 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 954.0 kB which makes up the majority of the site volume.
Potential reduce by 106.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 106.0 kB or 75% of the original size.
Potential reduce by 0 B
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. Janssen images are well optimized though.
Potential reduce by 231.5 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 231.5 kB or 54% of the original size.
Potential reduce by 47.8 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. Janssen.com.mx needs all CSS files to be minified and compressed as it can save up to 47.8 kB or 31% of the original size.
Number of requests can be reduced by 106 (89%)
119
13
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Janssen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
janssen.com.mx
408 ms
www.janssen.com
114 ms
fbevents.js
34 ms
system.base.css
63 ms
system.menus.theme.css
67 ms
system.messages.theme.css
65 ms
system.theme.css
66 ms
date.css
65 ms
datepicker.1.7.css
64 ms
aggregator.theme.css
66 ms
comment.theme.css
72 ms
node.css
97 ms
field.theme.css
74 ms
extlink.css
70 ms
views.css
77 ms
search.theme.css
94 ms
user.base.css
82 ms
user.theme.css
88 ms
ckeditor.css
94 ms
jquery.ui.core.min.css
101 ms
jquery.ui.theme.min.css
109 ms
jquery.ui.menu.min.css
115 ms
jquery.ui.autocomplete.min.css
139 ms
janssen_features.css
115 ms
janssen_latam.css
118 ms
apachesolr_autocomplete.css
126 ms
ctools.css
136 ms
covid-faq-global.css
135 ms
janssen-menu.css
140 ms
janssen-home.css
147 ms
panels.css
144 ms
take_over.css
157 ms
gatewayfilter.css
159 ms
contactfilter.css
160 ms
jquery-ui.css
53 ms
covid_faq.css
170 ms
productfilter.css
175 ms
templates.css
174 ms
screen.css
179 ms
BrightcoveExperiences_all.js
100 ms
jquery-ui.js
53 ms
jquery.min.js
132 ms
jquery-extend-3.4.0.js
139 ms
jquery-html-prefilter-3.5.0-backport.js
139 ms
jquery.once.js
142 ms
flags.js
140 ms
drupal.js
149 ms
no-js.js
153 ms
appscroll.js
155 ms
imagesloaded.pkgd.min.js
158 ms
modernizr.custom.74127.js
159 ms
purl.js
160 ms
underscore-min.js
155 ms
jquery.ui.core.min.js
161 ms
jquery.ui.widget.min.js
180 ms
jquery.ui.position.min.js
162 ms
jquery.ui.position-1.13.0-backport.js
157 ms
jquery.ui.menu.min.js
152 ms
jquery.ui.autocomplete.min.js
149 ms
jquery.cookie.js
165 ms
jquery.form.min.js
154 ms
ajax.js
155 ms
jquery_update.js
152 ms
extlink.js
143 ms
apachesolr_autocomplete_jqueryui.js
159 ms
janssenlocation.js
158 ms
janssen-news.js
163 ms
janssen-menu.js
162 ms
xml_export_import.js
148 ms
take_over.js
148 ms
gatewayfilter.js
152 ms
progress.js
156 ms
covid_faq.js
153 ms
autocomplete.js
165 ms
custom-select-menu.jquery.min.js
165 ms
screen-blessed2.css
142 ms
screen-blessed1.css
156 ms
jquery.bxslider.min.js
154 ms
lightbox.min.js
225 ms
janssen_misc.js
224 ms
janssen_mobile.js
223 ms
jquery.debouncedresize.js
222 ms
jquery.fancybox.pack.js
214 ms
jquery.fancybox-thumbs.js
210 ms
jquery.fancybox-media.js
204 ms
jquery.hammer.js
203 ms
jquery.hoverIntent.js
197 ms
jquery.knob.js
197 ms
jquery.tinysubpub.js
192 ms
jquery.throttledresize.js
182 ms
jj-util.js
180 ms
jj-sticky-filter-module.js
181 ms
jj-mobile-desktop-toggle-module.js
177 ms
jj-grid-module.js
175 ms
jj-carousel-row-module.js
163 ms
jj-related-content-carousel-module.js
216 ms
fancybox-defaults.js
187 ms
jj-footer-nav-module.js
184 ms
jj-mobile-nav-button-module.js
180 ms
jj-search-results-filter-module.js
182 ms
jj-social-media-dropdown-module.js
167 ms
jj-sub-navigation-module.js
165 ms
jj-tabs-module.js
163 ms
homebreakingnews.js
157 ms
analytics.js
102 ms
gtm.js
199 ms
Johnson-Johnson-Innovative-Medicine-logo.svg
80 ms
icon-search.png
79 ms
icon-search.png
79 ms
homepage_jnj_im-announcement.jpg
83 ms
homepage_jnj_im-announcement-mobile.jpg
81 ms
menu-leaf.png
78 ms
aboutus_image_1.png
174 ms
grandmother_laughing_with_granddaughter_364_high_0.jpg
86 ms
att31885.jpg
84 ms
logo-white.png
42 ms
icons-sd091d6374f.png
127 ms
JJ_Logo_White.svg
128 ms
Karbon-Medium.otf
130 ms
Karbon-Semibold.otf
131 ms
Karbon-Regular.otf
131 ms
ui-bg_flat_75_ffffff_40x100.png
35 ms
icon-search-red.png
70 ms
icon-close-x.png
69 ms
JohnsonText-Regular.ttf
60 ms
collect
56 ms
JohnsonText-Light.ttf
33 ms
janssen.com.mx 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
janssen.com.mx 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
janssen.com.mx 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
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 Janssen.com.mx 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 Janssen.com.mx 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.
janssen.com.mx
Open Graph description is not detected on the main page of Janssen. 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: