4 sec in total
736 ms
2.9 sec
362 ms
Visit moh.ps now to see the best up-to-date Moh content for Palestinian Territory and also check out these interesting facts you probably never knew about moh.ps
Palestinian,Ministry of Health,Palestinian Ministry of Health,وزارة الصحة, وزارة الصحة الفلسطينية,وزارة صحة فلسطين,وزارة الصحة فلسطينية
Visit moh.psWe analyzed Moh.ps page load time and found that the first response time was 736 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.
moh.ps performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value13.3 s
0/100
25%
Value11.5 s
5/100
10%
Value380 ms
70/100
30%
Value0.244
51/100
15%
Value17.9 s
3/100
10%
736 ms
90 ms
149 ms
91 ms
116 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 56% of them (60 requests) were addressed to the original Moh.ps, 32% (34 requests) were made to Static.xx.fbcdn.net and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Moh.ps.
Page size can be reduced by 612.7 kB (46%)
1.3 MB
732.5 kB
In fact, the total size of Moh.ps 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. 80% 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. Images take 604.5 kB which makes up the majority of the site volume.
Potential reduce by 92.7 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 28.9 kB, which is 26% 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 92.7 kB or 85% of the original size.
Potential reduce by 64.7 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. Obviously, Moh needs image optimization as it can save up to 64.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 313.9 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 313.9 kB or 68% of the original size.
Potential reduce by 141.4 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. Moh.ps needs all CSS files to be minified and compressed as it can save up to 141.4 kB or 83% of the original size.
Number of requests can be reduced by 62 (61%)
101
39
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
moh.ps
736 ms
bootstrap-reset.css
90 ms
style.css
149 ms
ticker-style.css
91 ms
stye_rtl.css
116 ms
font-awesome.css
117 ms
jquery-1.10.2.min.js
351 ms
jquery-ui-1.8.18.custom.css
134 ms
google_analytics_auto.js
134 ms
jquery.vticker.js
162 ms
jquery.cookie.js
183 ms
custom.js
179 ms
jquery-easing-1.3.js
175 ms
jquery.ticker.js
198 ms
bootstrap.min.js
214 ms
jquery-ui.min.js
454 ms
all.js
33 ms
bootstrap.css
79 ms
layerslider.css
89 ms
ga.js
85 ms
02.png
188 ms
palestine.png
186 ms
us.png
188 ms
logo.png
196 ms
s1.png
184 ms
s2.png
183 ms
s4.png
189 ms
s5.png
188 ms
1_1.jpg
192 ms
1_4.jpg
210 ms
1_3.jpg
629 ms
2-1.jpg
614 ms
03.png
208 ms
04.png
245 ms
332.jpg
671 ms
jiFZtcvoDsLYQSyrORwP7L1X_7oLAoHM2Dco42l2oboOv1uIk.jpg
670 ms
hAMbaHwD6a5xSBGOkreixLYS_5ySRdDtovy4Omw4hy6ZgZpm3.jpg
627 ms
wTyA44OhxcR1j8FESSAvtIKl_qpILB4fAFJMP3sHCj5EAArKK.jpg
674 ms
ldME2GPjwjSwdwWMbdof4yyN_vWGb6LMlklzuqML3n1aUyieI.jpg
674 ms
m5RLp29WD3L1roczcM9v7Bdz_KO9aPpcuOzmNFKU74AmGgFYU.jpg
673 ms
J5Ynj6FEX2MXnDputCYQcRGz_dt8jYekZsrN873w1XRDG64GR.jpg
673 ms
HhhYdWwVt9Yi7QN7YLNu2gT8_VaJhDRAxHjVBZDzxXyza8QMN.jpg
772 ms
fPkxfKFy479VjJVKIYxJWva5_wfnaoyrZjhu9Wip8rhqUWxUI.jpg
761 ms
ahb3PeOSYULT78u1JPIX7Moe_4ltrdE7mdgXPtzDK2VjokOYP.jpg
780 ms
li7.png
735 ms
11.jpg
884 ms
xW7KNaesga43DGMxcwXP38bu_FoT4z2ULXAIqsGzYezhW2xgC.jpg
766 ms
leZMMTpkEl6bEGVVORvAfrlE_KrbaFITxVQYMFATKGpspwZGg.jpg
840 ms
FXyUBoE2WkJHyXVDC3FueJ12_hOSKJ1uqjKGb6RfxQTGi6L8d.jpg
887 ms
v8HUnRKK9TwvmKRku2f5I41m_J3Jj8y5njIFwzXQIqEboAIyL.jpg
844 ms
logofooter.png
847 ms
sdk.js
15 ms
li1.png
786 ms
38.png
848 ms
39.png
848 ms
10.png
847 ms
36.png
850 ms
__utm.gif
42 ms
DINNextLTArabic.ttf
1569 ms
fontawesome-webfont.woff
1062 ms
fontawesome-webfont.woff
1059 ms
12.png
951 ms
14.png
949 ms
collect
438 ms
532 ms
xd_arbiter.php
382 ms
xd_arbiter.php
437 ms
analytics.js
371 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
523 ms
collect
19 ms
collect
12 ms
video.php
143 ms
kyEKgjk51ZE.css
54 ms
25TyHxL4s5_.css
71 ms
N-k91nHCZS2.css
56 ms
xgj7bXhJNEH.css
65 ms
DY6CRC1i1Bl.css
70 ms
o-mG5yFm_Th.css
83 ms
Czh0gDTFcBt.css
85 ms
q68gy-v_YMF.js
98 ms
FJmpeSpHpjS.js
123 ms
0wM5s1Khldu.js
93 ms
yasHAKDGNFx.js
137 ms
Oagsvfb4VWi.js
109 ms
1FCa-btixu2.js
111 ms
n6VgtouijQL.js
108 ms
7BE0CZr3HTs.js
106 ms
pQrUxxo5oQp.js
146 ms
IjqSyiwKeaX.js
152 ms
LTv6ZK-5zxz.js
155 ms
1QuX41zDRrx.js
179 ms
_UYztdBNTjs.js
179 ms
-7JBD_ybv4q.js
186 ms
HgJbVwzBr8E.js
176 ms
Jl64yqKpITf.js
181 ms
njO1TPvGzoR.js
183 ms
H3EKDTObx05.js
181 ms
1bNoFZUdlYZ.js
183 ms
12402673_1082551518453349_1320127773_n.jpg
211 ms
pzwyo2GOJzP.svg
117 ms
pjFzEJk5jm9.png
111 ms
l5aPruN9xMM.png
111 ms
b8XhdWI9eAN.js
155 ms
K_65vAc89SX.png
94 ms
K00K-UgnsKu.png
93 ms
OZFAYTv-ZUg.js
7 ms
I6-MnjEovm5.js
3 ms
moh.ps accessibility score
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.
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.
moh.ps 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
Page has valid source maps
moh.ps 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
AR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moh.ps can be misinterpreted by Google and other search engines. Our service has detected that Arabic 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 Moh.ps 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.
moh.ps
Open Graph data is detected on the main page of Moh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: