3.7 sec in total
406 ms
2.6 sec
627 ms
Welcome to mobian.global homepage info - get ready to check MOBIAN best content right away, or after learning these important things about mobian.global
Find the best parking spots, taxies and bikes at your destination. If you're going on a short trip, a long holiday or visit a city for a day, MOBIAN has all the options available for you.
Visit mobian.globalWe analyzed Mobian.global page load time and found that the first response time was 406 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 55% of websites can load faster.
mobian.global performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value14.5 s
0/100
25%
Value8.8 s
15/100
10%
Value1,060 ms
25/100
30%
Value0.891
3/100
15%
Value12.0 s
16/100
10%
406 ms
663 ms
76 ms
243 ms
19 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 42% of them (22 requests) were addressed to the original Mobian.global, 21% (11 requests) were made to Use.typekit.net and 13% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (872 ms) belongs to the original domain Mobian.global.
Page size can be reduced by 154.7 kB (5%)
3.3 MB
3.2 MB
In fact, the total size of Mobian.global main page is 3.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. 70% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 117.8 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 117.8 kB or 71% of the original size.
Potential reduce by 34.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. MOBIAN images are well optimized though.
Potential reduce by 2.7 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 64 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. Mobian.global has all CSS files already compressed.
Number of requests can be reduced by 12 (35%)
34
22
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MOBIAN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
mobian.global
406 ms
en
663 ms
gtm.js
76 ms
app.css
243 ms
mapbox-gl.css
19 ms
logo.svg
459 ms
search-container.svg
462 ms
app_store_outlined.svg
457 ms
google_play_outlined.svg
462 ms
mobihub.png
240 ms
app.svg
383 ms
apple-store-badge.svg
297 ms
google-play-badge.svg
454 ms
hub.png
501 ms
last_mile.png
502 ms
fb.svg
524 ms
instagram.svg
549 ms
linkedin.svg
550 ms
app.js
834 ms
js
33 ms
consent.js
156 ms
js
52 ms
css
54 ms
lvl5nle.css
111 ms
css2
66 ms
banner.no-autoblock.js
11 ms
background-home.jpg
527 ms
article1.jpeg
402 ms
article2.png
872 ms
article3.jpeg
625 ms
p.css
38 ms
chevron-white.svg
231 ms
d
5 ms
d
31 ms
d
37 ms
d
61 ms
d
60 ms
S6uyw4BMUTPHjx4wWw.ttf
88 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
88 ms
S6u8w4BMUTPHh30AXC-v.ttf
115 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
131 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
131 ms
d
85 ms
d
86 ms
d
110 ms
d
86 ms
d
109 ms
S6u8w4BMUTPHjxsAXC-v.ttf
131 ms
S6u_w4BMUTPHjxsI9w2_Gwfo.ttf
131 ms
js
33 ms
analytics.js
16 ms
collect
13 ms
collect
24 ms
mobian.global 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
ARIA input fields do not have accessible names
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.
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>).
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
mobian.global 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
mobian.global 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 Mobian.global 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 Mobian.global 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.
mobian.global
Open Graph description is not detected on the main page of MOBIAN. 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: