6.4 sec in total
183 ms
5.9 sec
294 ms
Click here to check amazing Mobio content for United States. Otherwise, check out these important facts you probably never knew about mobio.com
QIAGEN delivers Sample to Insights solutions that enable customers to unlock insights from the building blocks of life - DNA, RNA and proteins.
Visit mobio.comWe analyzed Mobio.com page load time and found that the first response time was 183 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mobio.com performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value21.6 s
0/100
25%
Value17.5 s
0/100
10%
Value4,550 ms
0/100
30%
Value0.759
6/100
15%
Value27.2 s
0/100
10%
183 ms
982 ms
131 ms
257 ms
223 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 51% of them (67 requests) were addressed to the original Mobio.com, 14% (19 requests) were made to Um.simpli.fi and 4% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (982 ms) belongs to the original domain Mobio.com.
Page size can be reduced by 1.2 MB (50%)
2.4 MB
1.2 MB
In fact, the total size of Mobio.com main page is 2.4 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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 40.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 40.0 kB or 81% of the original size.
Potential reduce by 104.5 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. Obviously, Mobio needs image optimization as it can save up to 104.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 756.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 756.5 kB or 73% of the original size.
Potential reduce by 277.5 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. Mobio.com needs all CSS files to be minified and compressed as it can save up to 277.5 kB or 85% of the original size.
Number of requests can be reduced by 72 (71%)
102
30
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
mobio.com
183 ms
mobio.com
982 ms
style.css
131 ms
quickshopping.css
257 ms
amazon.css
223 ms
mirasvit_searchindex.css
226 ms
qquoteadv.css
263 ms
addressvalidation.css
280 ms
jquery-ui.min.css
283 ms
prototype.js
380 ms
jquery-1.10.2.min.js
403 ms
noconflict.js
402 ms
ccard.js
350 ms
validation.js
376 ms
builder.js
400 ms
effects.js
440 ms
dragdrop.js
473 ms
controls.js
455 ms
slider.js
479 ms
js.js
512 ms
form.js
462 ms
translate.js
526 ms
cookies.js
528 ms
jquery.min.js
616 ms
underscore.js
567 ms
backbone.js
574 ms
form.js
639 ms
autocomplete.js
613 ms
modernizr.custom.min.js
601 ms
selectivizr.js
664 ms
matchMedia.js
670 ms
matchMedia.addListener.js
677 ms
enquire.js
702 ms
app.js
693 ms
jquery.cycle2.min.js
769 ms
jquery.cycle2.swipe.min.js
764 ms
slideshow.js
768 ms
css
56 ms
dpx.js
26 ms
styles.css
839 ms
madisonisland.css
658 ms
imagesloaded.js
574 ms
minicart.js
646 ms
validationform.js
654 ms
jquery-ui.min.js
723 ms
jquery.ui.widget.js
593 ms
block_toggle.js
606 ms
analytics.js
164 ms
logo.png
186 ms
iso_icon.jpg
180 ms
top_icons_set.jpg
184 ms
icon_sprite.png
184 ms
button_search.png
178 ms
homepage-topbanner-Protein2.jpg
522 ms
homepage-topbanner-big-1.jpg
311 ms
homepage-topbanner-Mint.jpg
815 ms
homepage-topbanner-big-3.jpg
366 ms
homepage-topbanner-microbiome.jpg
312 ms
13997-50_1.jpg
265 ms
27800.jpg
358 ms
ads-product-3.png
462 ms
tails.png
386 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
161 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
180 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
200 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
242 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
241 ms
masthead.jpg
447 ms
san-antonio64th_web.png
455 ms
social_icons.png
453 ms
list-image_2.jpg
540 ms
img_5645_small.jpg
524 ms
edamame2015group3-21small.jpg
523 ms
widgets.js
207 ms
footer-map.png
529 ms
social_icons_footer.png
576 ms
button.ls
361 ms
p
45 ms
collect
21 ms
dpx
26 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
29 ms
match_redirect
25 ms
syndication
106 ms
318863852219531264
98 ms
29931
77 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
28 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
62 ms
match_redirect
4 ms
tinysquarelogo_webversion_normal.jpg
134 ms
CcZJL9CW4AEhBmE.jpg:small
162 ms
CcZpPCXWoAAeSIP.png:small
273 ms
tpid=C629559EDAC6D556EB75D10002D55490
20 ms
lr
9 ms
lr.gif
31 ms
match_redirect
4 ms
sync
20 ms
match_redirect
3 ms
C629559EDAC6D556EB75D10002D55490
79 ms
jot
27 ms
match_redirect
4 ms
ProfilesEngineServlet
34 ms
ProfilesEngineServlet
972 ms
match_redirect
4 ms
engine
89 ms
42 ms
spotx_match
16 ms
fb_match
4 ms
u.php
114 ms
75 ms
33 ms
an
4 ms
lj_match
4 ms
exelate
6 ms
cw_match
5 ms
rb_match
5 ms
rtset
65 ms
ox_match
12 ms
pm_match
5 ms
Pug
52 ms
pixel
45 ms
sd
11 ms
g_match
5 ms
match_redirect
4 ms
pixel
22 ms
aa_px
3 ms
tap.php
425 ms
tap.php
411 ms
drawbutton.ls
619 ms
embedbutton.css
53 ms
embedbutton.js
370 ms
jsonmin.js
316 ms
resource.js
321 ms
mobio.com 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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
mobio.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
Missing source maps for large first-party JavaScript
mobio.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobio.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 Mobio.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.
mobio.com
Open Graph description is not detected on the main page of Mobio. 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: