7.1 sec in total
1 sec
6 sec
75 ms
Welcome to inwi.ma homepage info - get ready to check Inwi best content for Morocco right away, or after learning these important things about inwi.ma
Un max d'avantage avec inwi Maroc. inwi propose des offres et services, pour les professionnelles comme pour les particuliers de téléphonie mobile, d'internet et de fibre
Visit inwi.maWe analyzed Inwi.ma page load time and found that the first response time was 1 sec and then it took 6.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.
inwi.ma performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value25.1 s
0/100
25%
Value18.8 s
0/100
10%
Value3,050 ms
2/100
30%
Value0.009
100/100
15%
Value26.3 s
0/100
10%
1031 ms
301 ms
549 ms
670 ms
357 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 86% of them (64 requests) were addressed to the original Inwi.ma, 14% (10 requests) were made to Api.inwi.ma. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Api.inwi.ma.
Page size can be reduced by 248.6 kB (5%)
4.8 MB
4.5 MB
In fact, the total size of Inwi.ma main page is 4.8 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 190.6 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 190.6 kB or 88% of the original size.
Potential reduce by 54.3 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. Inwi images are well optimized though.
Potential reduce by 3.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.7 kB or 90% of the original size.
Number of requests can be reduced by 61 (84%)
73
12
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inwi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and as a result speed up the page load time.
inwi.ma
1031 ms
inwiprodmaxyzqr.js
301 ms
inwiprodmaxyzqr.js
549 ms
ruxitagentjs_ICANVfghqrux_10287240325103108.js
670 ms
3b42dcb9893091ef.css
357 ms
polyfills-c67a75d1b6f99dc8.js
598 ms
53124-8df3e9bb7860958c.js
421 ms
7485-8d9e76f5bcba6e03.js
477 ms
30400-af09a481ad75e67f.js
531 ms
31812-f07fd615316bdb7e.js
594 ms
86886-12ac252dd697e64f.js
645 ms
41664-9179ee6336959b0a.js
661 ms
89755-688dbc8b8bc23c06.js
729 ms
25675-050dc0ad9fe646fa.js
730 ms
36260.17a2e6e29faf60e9.js
756 ms
31296.f1f74ab0dac96529.js
783 ms
77918-a1671dd8ca89a025.js
787 ms
78897-f9e79914dfa12675.js
835 ms
95520-34e96a342cedcb2f.js
848 ms
7463-7a71a4d710514971.js
865 ms
60556-a6a69c321c9078c1.js
890 ms
60594-2e2b85119877c965.js
899 ms
65987.c0e9599484b83ea3.js
904 ms
78676.c5205ef1ad4b9995.js
957 ms
73528.d2a9a521daa5c292.js
969 ms
74356.25cedc6ffde5dca6.js
973 ms
96462.05683dcd9b5fd462.js
1012 ms
77514.bd01d10f29959419.js
1016 ms
72009.bfa63a86be24fe22.js
1018 ms
116.07df30fc2ed19057.js
1074 ms
22193.0ff0096face2456a.js
1089 ms
9145.fec7358ff71f68e5.js
1078 ms
93699.dd82b806f5a22224.js
1143 ms
35941.e9ae40e8b96ab1d4.js
1134 ms
94970.2242e5175a29475a.js
1158 ms
47439.9e16fafc0cd3ebdc.js
1190 ms
53546.c5ce1fb7f35befa6.js
892 ms
85895.886c068aef32db7a.js
858 ms
54003.b40d17dc6253e54b.js
834 ms
10357.60a7a2622058a05d.js
790 ms
43093.1eeb534d52a66820.js
749 ms
46066-c8fd307243fc3f3d.js
786 ms
95815.b1437841535cfd03.js
773 ms
32185.bda819b48490d601.js
741 ms
36884.e7639dabc73a2c23.js
773 ms
64891.6f24afec8552699b.js
741 ms
14067.03792774245e7f10.js
743 ms
ADSL-793x873.png
1891 ms
ADSL-359x549.png
1088 ms
793X873_1_.png
4407 ms
359X549_2_.png
1551 ms
_6-793x873.png
2627 ms
_6-359x549.png
1525 ms
793x873_1__2.png
1873 ms
359x549_2_.png
1915 ms
win_793x873.png
2478 ms
win_359x549.png
2012 ms
99339.bafe07c78789f498.js
719 ms
49068.8b735edff2f0b5c1.js
706 ms
92354.9287a2f7b812bed3.js
728 ms
19718.f56b6d179351e0d7.js
740 ms
24929.e42d24acf3665443.js
718 ms
34060.047fc255f89a93dd.js
733 ms
62796.4dee8c5a5469008e.js
710 ms
16442.4133f4397018af6b.js
714 ms
6641.1c32a4d559758c6d.js
713 ms
webpack-3f7b8f5aabd54b23.js
723 ms
framework-2f021977c006fe27.js
833 ms
main-9f76ba24e06c87e4.js
737 ms
_app-5842a2ec6b710fc1.js
901 ms
index-3af60e6f67945f0f.js
712 ms
_buildManifest.js
736 ms
_ssgManifest.js
718 ms
inwiprodmaxyzqr.js
1409 ms
inwi.ma 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-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
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
[id] attributes on active, focusable elements are not unique
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
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>).
inwi.ma best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
inwi.ma SEO score
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
![]()
FR
![]()
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inwi.ma can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Inwi.ma 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.
inwi.ma
Open Graph data is detected on the main page of Inwi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: