7.7 sec in total
597 ms
6.9 sec
167 ms
Click here to check amazing Mobilis content for Algeria. Otherwise, check out these important facts you probably never knew about mobilis.dz
Mobilis est le premier opérateur mobile en Algérie, compte actuellement plus de 18 millions d'abonnés
Visit mobilis.dzWe analyzed Mobilis.dz page load time and found that the first response time was 597 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mobilis.dz performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value33.3 s
0/100
25%
Value20.2 s
0/100
10%
Value990 ms
27/100
30%
Value0.009
100/100
15%
Value14.3 s
9/100
10%
597 ms
343 ms
455 ms
728 ms
343 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 90% of them (46 requests) were addressed to the original Mobilis.dz, 6% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Mobilis.dz.
Page size can be reduced by 1.2 MB (21%)
5.7 MB
4.5 MB
In fact, the total size of Mobilis.dz main page is 5.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. 45% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 35.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. This page needs HTML code to be minified as it can gain 15.2 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.0 kB or 84% of the original size.
Potential reduce by 320.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. Mobilis images are well optimized though.
Potential reduce by 803.1 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 803.1 kB or 71% of the original size.
Potential reduce by 34.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. Mobilis.dz needs all CSS files to be minified and compressed as it can save up to 34.5 kB or 84% of the original size.
Number of requests can be reduced by 25 (50%)
50
25
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobilis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
mobilis.dz
597 ms
normalize.css
343 ms
style.css
455 ms
jquery-1.11.0.min.js
728 ms
Popup.css
343 ms
Popup.js
345 ms
style_detail.css
444 ms
r.js
674 ms
0828ebca97ab180066deeacd255e15ee05269a3bc79bee28fbb790ca47a51bf2.js
2012 ms
js
57 ms
respond.js
594 ms
rem.min.js
692 ms
swipe.js
799 ms
fastclick.js
1018 ms
components.js
931 ms
img.srcset.js
957 ms
jquery.js
1250 ms
jquery.validationEngine-fr.js
1136 ms
jquery.validationEngine.js
1274 ms
gtm.js
41 ms
ga.js
22 ms
__utm.gif
24 ms
js
92 ms
mobilis.jpg
160 ms
logo-poste.png
157 ms
logo_cib_satim.png
341 ms
facebook.svg
345 ms
youtube.png
342 ms
twitter.svg
343 ms
linkedin.svg
452 ms
instagram_new.png
454 ms
logo.svg
683 ms
view-list.svg
681 ms
man.svg
679 ms
men.svg
684 ms
time.svg
788 ms
support-new.jpg
790 ms
go.svg
1015 ms
m2m.jpg
1453 ms
tune.svg
1017 ms
plus-gray.svg
1018 ms
store_new.png
1133 ms
catalogue_b2b_pc.jpg
2193 ms
twenty_Pc.jpg
1878 ms
twentypc.jpg
3102 ms
SAMA_4G_MAN_PC.jpg
2322 ms
cridilis_pc_ar.jpg
3667 ms
sama_control_1500_pc_fr.jpg
3100 ms
sama_net_ram_1500_pc_fr.jpg
2536 ms
sama_net_ram_2000_pc_ram_fr.jpg
2970 ms
HelveticaNeue-lt.woff
2742 ms
mobilis.dz 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.
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
mobilis.dz 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mobilis.dz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobilis.dz can be misinterpreted by Google and other search engines. Our service has detected that French 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 Mobilis.dz 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.
mobilis.dz
Open Graph description is not detected on the main page of Mobilis. 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: