2.8 sec in total
567 ms
2 sec
212 ms
Visit mobile.fares.net now to see the best up-to-date Mobile Fares content for Egypt and also check out these interesting facts you probably never knew about mobile.fares.net
الساحة العربية أكبر تجمع عربي على الإنترنت وأول موقع عربي للحوار المباشر و غير المباشر من فارس نت وجسور
Visit mobile.fares.netWe analyzed Mobile.fares.net page load time and found that the first response time was 567 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
mobile.fares.net performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value1.6 s
99/100
25%
Value2.4 s
98/100
10%
Value90 ms
98/100
30%
Value0
100/100
15%
Value5.4 s
72/100
10%
567 ms
45 ms
67 ms
68 ms
14 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 28% of them (13 requests) were addressed to the original Mobile.fares.net, 17% (8 requests) were made to Fares.net and 11% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Khayr.net.
Page size can be reduced by 109.7 kB (18%)
593.7 kB
484.0 kB
In fact, the total size of Mobile.fares.net main page is 593.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 401.0 kB which makes up the majority of the site volume.
Potential reduce by 10.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 10.8 kB or 73% of the original size.
Potential reduce by 17.8 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. Mobile Fares images are well optimized though.
Potential reduce by 41.8 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 41.8 kB or 32% of the original size.
Potential reduce by 39.2 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. Mobile.fares.net needs all CSS files to be minified and compressed as it can save up to 39.2 kB or 84% of the original size.
Number of requests can be reduced by 13 (34%)
38
25
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Fares. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
mobile.fares.net
567 ms
jquery.min.js
45 ms
fares.css
67 ms
oil.css
68 ms
adsbygoogle.js
14 ms
faresnetlogo.png
31 ms
eyoon.png
31 ms
khayr.png
32 ms
athkar.png
33 ms
twitterOFF.png
33 ms
instagramOFF.png
34 ms
lateef.css
23 ms
droidarabicnaskh.css
38 ms
droidarabickufi.css
44 ms
bg_dark2.png
44 ms
how-to-grow-twitter-followers.jpg
82 ms
app.svg
1355 ms
gtm.js
49 ms
Oil.png
129 ms
large.png
158 ms
athkar200.png
144 ms
khayr200.png
60 ms
bg_dark.png
62 ms
App.png
195 ms
ca-pub-9075300815474646.js
57 ms
zrt_lookup.html
59 ms
show_ads_impl.js
66 ms
HelveticaNeueW23-Reg.woff
265 ms
HelveticaNeueW23-Bd.woff
131 ms
DroidKufi-Regular.woff
40 ms
DroidKufi-Bold.woff
47 ms
geflowregular.ttf
116 ms
analytics.js
78 ms
ads
256 ms
osd.js
15 ms
collect
14 ms
collect
49 ms
HelveticaNeueW23-Reg.ttf
111 ms
m_js_controller.js
22 ms
abg.js
44 ms
favicon
67 ms
googlelogo_color_112x36dp.png
26 ms
nessie_icon_thin_arrow_big_white.png
22 ms
s
10 ms
x_button_blue2.png
3 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
8 ms
mobile.fares.net 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-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
mobile.fares.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
mobile.fares.net 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
AR
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.fares.net can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it matches the claimed language. Our system also found out that Mobile.fares.net 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.
mobile.fares.net
Open Graph data is detected on the main page of Mobile Fares. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: