9 sec in total
1.2 sec
6.8 sec
981 ms
Visit mobilitybuy.com now to see the best up-to-date Mobilitybuy content and also check out these interesting facts you probably never knew about mobilitybuy.com
mobility news about disabled shops and buy products publishing articles from around the world
Visit mobilitybuy.comWe analyzed Mobilitybuy.com page load time and found that the first response time was 1.2 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
mobilitybuy.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value8.0 s
2/100
25%
Value5.0 s
64/100
10%
Value320 ms
76/100
30%
Value0
100/100
15%
Value5.4 s
71/100
10%
1180 ms
118 ms
163 ms
171 ms
151 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 26% of them (29 requests) were addressed to the original Mobilitybuy.com, 8% (9 requests) were made to Apis.google.com and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Mobilitybuy.com.
Page size can be reduced by 845.5 kB (64%)
1.3 MB
479.7 kB
In fact, the total size of Mobilitybuy.com main page is 1.3 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. Javascripts take 634.4 kB which makes up the majority of the site volume.
Potential reduce by 112.3 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 112.3 kB or 78% of the original size.
Potential reduce by 2.6 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. Mobilitybuy images are well optimized though.
Potential reduce by 381.0 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 381.0 kB or 60% of the original size.
Potential reduce by 349.6 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. Mobilitybuy.com needs all CSS files to be minified and compressed as it can save up to 349.6 kB or 81% of the original size.
Number of requests can be reduced by 67 (70%)
96
29
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobilitybuy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.mobilitybuy.com
1180 ms
dcssb.css
118 ms
jquery-ui-1.10.3.custom.css
163 ms
jquery-ui-spinner.css
171 ms
calendar-jos.css
151 ms
form_maker_frontend.css
168 ms
css
38 ms
genericons.css
262 ms
style.css
340 ms
jquery.js
354 ms
jquery-migrate.min.js
326 ms
js
53 ms
if_gmap_front_end.js
347 ms
jelly.min.js
326 ms
file-upload.js
393 ms
calendar.js
431 ms
calendar_function.js
420 ms
ga.social_tracking.js
441 ms
jquery.social.float.1.3.js
444 ms
adsbygoogle.js
26 ms
q
47 ms
widgets.js
101 ms
in.js
35 ms
pinit.js
71 ms
widget.min.js
420 ms
core.min.js
472 ms
mouse.min.js
493 ms
slider.min.js
507 ms
button.min.js
507 ms
spinner.min.js
545 ms
effect.min.js
554 ms
effect-shake.min.js
627 ms
functions.js
630 ms
Levate-300x263.jpg
243 ms
image-5762574-10693443
29 ms
poweredby_000000.gif
30 ms
wpid-NPD2014-300x100.jpg
201 ms
wpid-David-and-Justine-Greening-300x177.jpg
241 ms
10693443-1456311781600
22 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
21 ms
BTu4SsVveqk58cdYjlaM9g.ttf
51 ms
zpv3sOKAbMf4wff105oLjw.ttf
50 ms
5pEc4QKTMA2oB4Hi9NkS4w.ttf
35 ms
VqvVqv1mv0Gr1Gr9Frul7xuyp+V8XvqnTyb1UoNRm4Af+FsAGNAEuwCFBYsQEBjlmxRgYrWCGwEFlLsBRSWCGwgFkdsAYrXFhZsBQrAAAAAVLP0T8AAA==
18 ms
ca-pub-8354097961453019.js
74 ms
zrt_lookup.html
69 ms
show_ads_impl.js
70 ms
branding.css
84 ms
ads
415 ms
Rb9PotDMAes
199 ms
osd.js
55 ms
branding.css
83 ms
ads
550 ms
ads
518 ms
q
225 ms
json
459 ms
ads
437 ms
all.js
17 ms
plusone.js
120 ms
secureAnonymousFramework
242 ms
www-embed-player-vflfNyN_r.css
363 ms
www-embed-player.js
438 ms
base.js
962 ms
389 ms
xd_arbiter.php
57 ms
xd_arbiter.php
106 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
373 ms
pinit_main.js
289 ms
cb=gapi.loaded_0
34 ms
cb=gapi.loaded_1
65 ms
fastbutton
131 ms
q
260 ms
q
260 ms
q
295 ms
q
372 ms
postmessageRelay
291 ms
m_js_controller.js
308 ms
abg.js
399 ms
cb=gapi.loaded_0
202 ms
cb=gapi.loaded_1
199 ms
share
314 ms
sprite_connect_v14.png
328 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
297 ms
like.php
217 ms
count.json
354 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
80 ms
3193398744-postmessagerelay.js
271 ms
rpc:shindig_random.js
129 ms
css
81 ms
favicon
321 ms
favicon
380 ms
googlelogo_color_112x36dp.png
321 ms
favicon
370 ms
nessie_icon_tiamat_white.png
182 ms
search-widget-sprite.png
497 ms
loader._V1381159565_.gif
187 ms
qeKvIRsJabD.js
344 ms
LVx-xkvaJ0b.png
349 ms
s
87 ms
x_button_blue2.png
138 ms
jot
315 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
54 ms
cb=gapi.loaded_0
89 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
113 ms
ad_status.js
115 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
11 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
10 ms
fastbutton
95 ms
tab_bottom_floating.png
112 ms
ui
16 ms
like.php
110 ms
qeKvIRsJabD.js
6 ms
mobilitybuy.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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
mobilitybuy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
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
mobilitybuy.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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 Mobilitybuy.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 Mobilitybuy.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.
mobilitybuy.com
Open Graph data is detected on the main page of Mobilitybuy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: