mofa.gov.iq

mofa.gov.iq is SSL secured

Free website and domain report on mofa.gov.iq

Last Updated: 1st April, 2021 Update Now
Overview

Snoop Summary for mofa.gov.iq

This is a free and comprehensive report about mofa.gov.iq. The domain mofa.gov.iq is currently hosted on a server located in Singapore in Singapore with the IP address 13.67.50.87, where SGD is the local currency and the local language is Mandarin. Mofa.gov.iq has the potential to be earning an estimated $8 USD per day from advertising revenue. If mofa.gov.iq was to be sold it would possibly be worth $6,018 USD (based on the daily revenue potential of the website over a 24 month period). Mofa.gov.iq is quite popular with an estimated 2,888 daily unique visitors. This report was last updated 1st April, 2021.

About mofa.gov.iq

Site Preview: mofa.gov.iq mofa.gov.iq
Title: وزارة الخارجية العراقية - وزارة الخارجية العراقية
Description: وزارة الخارجية العراقية
Keywords and Tags: government, military
Related Terms: mofa
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

2/5

Valuation

$6,018 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 201,081
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 2,888
Monthly Visitors: 87,902
Yearly Visitors: 1,054,120
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $8 USD
Monthly Revenue: $251 USD
Yearly Revenue: $3,004 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: mofa.gov.iq 11
Domain Name: mofa 4
Extension (TLD): goviq 5

Page Speed Analysis

Average Load Time: 2.49 seconds
Load Time Comparison: Faster than 34% of sites

PageSpeed Insights

Avg. (All Categories) 75
Performance 79
Accessibility 94
Best Practices 93
SEO 83
Progressive Web App 27
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://www.mofa.gov.iq/
Updated: 1st April, 2021

2.78 seconds
First Contentful Paint (FCP)
5%
77%
18%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
79

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for mofa.gov.iq. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 50 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 1.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 90 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive mofa.gov.iq as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mofa.gov.iq/
http/1.1
0
2616.138999816
366
0
302
text/html
http://www.mofa.gov.iq/
http/1.1
2616.7199998163
3888.0500001833
18429
111024
200
text/html
Document
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-brands-400.woff2?v=5.15.2
http/1.1
3904.0359999053
4856.8040002137
78803
78472
200
font/woff2
Font
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-regular-400.woff2?v=5.15.2
http/1.1
3904.1590001434
4394.2900002003
13918
13588
200
font/woff2
Font
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-solid-900.woff2?v=5.15.2
http/1.1
3904.3859997764
4880.8630001731
80583
80252
200
font/woff2
Font
http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,300italic,300,400italic,600&subset=latin,latin-ext
http/1.1
3907.9430000857
3962.9250001162
1418
11179
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-includes/css/dist/block-library/style-rtl.min.css,qver=5.6.2.pagespeed.ce.3h8fyPnXJ_.css
http/1.1
3908.100000117
4183.5159999318
8248
51161
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-content/plugins/google-analytics-for-wordpress/assets/css/A.frontend.min.css,qver=7.16.1.pagespeed.cf.EwuLFDn4Lq.css
http/1.1
3908.2940001972
4365.2349999174
1238
7694
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.main.min.css,qver=3.7.4.pagespeed.cf.7_4OumCqVs.css
http/1.1
3908.6250001565
6426.4600002207
18519
95245
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.font-awesome.min.css,qver=3.7.4.pagespeed.cf.OvW0GmWfVe.css
http/1.1
3908.8519997895
6202.6450000703
13033
59347
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
http/1.1
3909.037000034
4591.9449999928
31278
89410
200
application/javascript
Script
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery-migrate.min.js,qver=3.3.2.pagespeed.jm.Ws-UgblvVg.js
http/1.1
3909.1619998217
4404.6370000578
4557
11126
200
application/javascript
Script
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/libs/jquery.flexslider.min.js,qver=3.7.4.pagespeed.ce.LA3M-6Qd69.js
http/1.1
6463.5029998608
6766.3130001165
7084
23103
200
application/javascript
Script
http://www.mofa.gov.iq/wp-content/uploads/2019/07/xHeader-Image-AR.jpg.pagespeed.ic.c1_k64Q0Js.webp
http/1.1
6485.1990002207
6764.7000001743
15555
15066
200
image/webp
Image
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
http/1.1
6485.9629999846
8823.3989998698
305689
305385
200
image/jpeg
Image
http://www.mofa.gov.iq/wp-content,_plugins,_pdf-viewer-block,_public,_js,_pdf-viewer-block.js,qver==5.6.2+wp-includes,_js,_underscore.min.js,qver==1.8.3.pagespeed.jc.bQNP40F31e.js
http/1.1
6203.9899998344
6462.8309998661
6486
17148
200
application/javascript
Script
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
http/1.1
6486.2110000104
6962.846999988
21369
75631
200
application/javascript
Script
http://www.mofa.gov.iq/wp-includes/js/wp-emoji-release.min.js?ver=5.6.2
http/1.1
6486.3450000994
6764.2149999738
5004
14110
200
application/javascript
Script
http://fonts.gstatic.com/s/sourcesanspro/v14/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2
http/1.1
6595.1999998651
6598.7430000678
13715
13324
200
font/woff2
Font
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu3cOWxw.woff2
http/1.1
6665.4969998635
6668.7960000709
13499
13108
200
font/woff2
Font
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdu3cOWxw.woff2
http/1.1
6667.2359998338
6670.4750000499
13614
13224
200
font/woff2
Font
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-720x340.jpeg.pagespeed.ic.sDUmhgWSP5.webp
http/1.1
6794.722000137
7283.9520000853
21817
21294
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xIMG-20210331-WA0012-1-720x340.jpg.pagespeed.ic.EQiekG_Imm.webp
http/1.1
6794.9190000072
7067.6489998586
15603
15100
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-720x340.jpeg.pagespeed.ic.nSqft41m_m.webp
http/1.1
6795.0619999319
7565.7230000943
29895
29360
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x1-720x340.jpg.pagespeed.ic.wKspkvD5o5.webp
http/1.1
6796.0870000534
7599.6469999664
21130
20646
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-720x340.jpg.pagespeed.ic.d8lrQQamTv.webp
http/1.1
6796.4119999669
7620.7280000672
28001
27510
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x9C3732A4-B6E2-4A94-9905-01DCD313C151-720x340.jpeg.pagespeed.ic.K0Kd6CyXQE.webp
http/1.1
6796.564000193
7370.2560001984
35615
35096
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-80x80.jpeg.pagespeed.ic.LZDTBaBeC1.webp
http/1.1
6796.7759999447
7373.6310000531
2454
1934
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xIMG-20210331-WA0012-1-80x80.jpg.pagespeed.ic.UUSBRP5kjf.webp
http/1.1
6796.9599999487
7095.6640001386
2331
1832
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-80x80.jpeg.pagespeed.ic.aoh8oQ6YyH.webp
http/1.1
6798.2210000046
7093.6250002123
2592
2062
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x1-80x80.jpg.pagespeed.ic.FucmGIUXTM.webp
http/1.1
6798.448999878
7372.0720000565
2282
1802
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-80x80.jpg.pagespeed.ic.NnA5_AREE4.webp
http/1.1
6799.0330001339
7372.6039999165
2529
2042
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xC86BE556-F9A2-4B35-8277-77B5DA16456A-80x80.jpeg.pagespeed.ic.8fmVCRwwQb.webp
http/1.1
6801.3450000435
7092.7780000493
2377
1862
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/03/x071754E3-B53F-4383-A87D-72D815B08B12-80x80.jpeg.pagespeed.ic.EjNqPh3YAb.webp
http/1.1
6801.5499999747
7372.9770001955
1772
1256
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_0295-80x80.jpg.pagespeed.ic.M-oglodBLh.webp
http/1.1
6801.8000000156
7371.1270000786
2757
2270
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xphoto_2021-03-20_19-55-36-80x80.jpg.pagespeed.ic.-BcVrMUFlg.webp
http/1.1
6802.0020001568
7373.3430001885
2594
2090
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_0609-80x80.jpg.pagespeed.ic.Pt0z9vjJuy.webp
http/1.1
6802.1760000847
7371.5920001268
2007
1520
200
image/webp
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_1232-720x340.jpg.pagespeed.ic.m31Im30YVD.webp
http/1.1
7674.3919998407
8162.7529999241
34084
33594
200
image/webp
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
3924.892
7.798
3996.496
104.032
4436.657
57.159
6458.157
35.733
6499.169
25.633
6524.818
303.08
6828.681
66.559
6903.874
100.055
7004.791
5.232
7015.624
93.333
7111.491
117.726
7229.388
70.238
7411.479
106.357
7517.859
7.198
7551.623
43.765
7605.154
29.063
7634.254
70.588
7851.574
42.826
8168.264
25.528
8252.314
41.564
8384.866
9.355
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mofa.gov.iq should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mofa.gov.iq should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mofa.gov.iq should consider minifying JS files.
Remove unused CSS — Potential savings of 27 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mofa.gov.iq should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.main.min.css,qver=3.7.4.pagespeed.cf.7_4OumCqVs.css
18519
14532
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.font-awesome.min.css,qver=3.7.4.pagespeed.cf.OvW0GmWfVe.css
13033
12882
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images — Potential savings of 195 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
305385
200175
Serve images in next-gen formats — Potential savings of 233 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
305385
238141
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Mofa.gov.iq should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mofa.gov.iq/
190
http://www.mofa.gov.iq/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mofa.gov.iq should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 9 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
9461
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://www.mofa.gov.iq/wp-content/uploads/2019/07/xHeader-Image-AR.jpg.pagespeed.ic.c1_k64Q0Js.webp
0

Diagnostics

Avoids enormous network payloads — Total size was 862 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
305689
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-solid-900.woff2?v=5.15.2
80583
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-brands-400.woff2?v=5.15.2
78803
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x9C3732A4-B6E2-4A94-9905-01DCD313C151-720x340.jpeg.pagespeed.ic.K0Kd6CyXQE.webp
35615
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_1232-720x340.jpg.pagespeed.ic.m31Im30YVD.webp
34084
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
31278
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-720x340.jpeg.pagespeed.ic.nSqft41m_m.webp
29895
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-720x340.jpg.pagespeed.ic.d8lrQQamTv.webp
28001
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-720x340.jpeg.pagespeed.ic.sDUmhgWSP5.webp
21817
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
21369
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mofa.gov.iq should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.5 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://www.mofa.gov.iq/
799.237
192.951
59.875
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
536.437
287.974
1.521
Unattributable
144.79
1.113
0.215
Minimizes main-thread work — 1.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
492.734
Style & Layout
419.95
Other
301.463
Rendering
207.08
Script Parsing & Compilation
68.029
Parse HTML & CSS
25
Keep request counts low and transfer sizes small — 38 requests • 862 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
38
882245
Image
19
531084
Font
6
214132
Script
6
75778
Stylesheet
5
42456
Document
1
18429
Other
1
366
Media
0
0
Third-party
4
42246
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
42246
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 9 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://www.mofa.gov.iq/
527
152
http://www.mofa.gov.iq/
423
104
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
2120
93
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
1380
70
http://www.mofa.gov.iq/wp-content,_plugins,_pdf-viewer-block,_public,_js,_pdf-viewer-block.js,qver==5.6.2+wp-includes,_js,_underscore.min.js,qver==1.8.3.pagespeed.jc.bQNP40F31e.js
1520
67
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
2213
59
Unattributable
190
57
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
2273
53
http://www.mofa.gov.iq/
679
50
Avoid non-composited animations — 5 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element
a
img
img

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Largest Contentful Paint — 1.4 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.127
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 1.0 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 370 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mofa.gov.iq should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,300italic,300,400italic,600&subset=latin,latin-ext
1418
190
http://www.mofa.gov.iq/wp-includes/css/dist/block-library/style-rtl.min.css,qver=5.6.2.pagespeed.ce.3h8fyPnXJ_.css
8248
110
http://www.mofa.gov.iq/wp-content/plugins/google-analytics-for-wordpress/assets/css/A.frontend.min.css,qver=7.16.1.pagespeed.cf.EwuLFDn4Lq.css
1238
110
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.main.min.css,qver=3.7.4.pagespeed.cf.7_4OumCqVs.css
18519
190
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.font-awesome.min.css,qver=3.7.4.pagespeed.cf.OvW0GmWfVe.css
13033
150
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
31278
230
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery-migrate.min.js,qver=3.3.2.pagespeed.jm.Ws-UgblvVg.js
4557
110
Properly size images — Potential savings of 346 KiB
Images can slow down the page's load time. Mofa.gov.iq should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
305385
248572
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-720x340.jpeg.pagespeed.ic.nSqft41m_m.webp
29360
23932
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-720x340.jpg.pagespeed.ic.d8lrQQamTv.webp
27510
22424
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-720x340.jpeg.pagespeed.ic.sDUmhgWSP5.webp
21294
17357
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x1-720x340.jpg.pagespeed.ic.wKspkvD5o5.webp
20646
16829
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xIMG-20210331-WA0012-1-720x340.jpg.pagespeed.ic.EQiekG_Imm.webp
15100
12308
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x9C3732A4-B6E2-4A94-9905-01DCD313C151-720x340.jpeg.pagespeed.ic.K0Kd6CyXQE.webp
35096
6487
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_1232-720x340.jpg.pagespeed.ic.m31Im30YVD.webp
33594
6210

Diagnostics

Avoid an excessive DOM size — 876 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
876
Maximum DOM Depth
img
17
Maximum Child Elements
89

Metrics

Speed Index — 5.1 s
The time taken for the page contents to be visibly populated.

Opportunities

Reduce initial server response time — Root document took 1,270 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://www.mofa.gov.iq/
1272.326

Diagnostics

Serve static assets with an efficient cache policy — 6 resources found
Mofa.gov.iq can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
0
305689
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-solid-900.woff2?v=5.15.2
0
80583
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-brands-400.woff2?v=5.15.2
0
78803
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-regular-400.woff2?v=5.15.2
0
13918
http://www.mofa.gov.iq/wp-includes/js/wp-emoji-release.min.js?ver=5.6.2
158000
5004
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
186000
21369
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
http://fonts.gstatic.com/s/sourcesanspro/v14/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2
3.543000202626
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu3cOWxw.woff2
3.2990002073348
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdu3cOWxw.woff2
3.2390002161264
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
img
94

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mofa.gov.iq. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Mofa.gov.iq may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-hidden="true"]` elements contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
93

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that mofa.gov.iq should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Underscore
1.8.3
FlexSlider
WordPress
5.6.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 37 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://mofa.gov.iq/
Allowed
http://www.mofa.gov.iq/
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-brands-400.woff2?v=5.15.2
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-regular-400.woff2?v=5.15.2
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-solid-900.woff2?v=5.15.2
Allowed
http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,300italic,300,400italic,600&subset=latin,latin-ext
Allowed
http://www.mofa.gov.iq/wp-includes/css/dist/block-library/style-rtl.min.css,qver=5.6.2.pagespeed.ce.3h8fyPnXJ_.css
Allowed
http://www.mofa.gov.iq/wp-content/plugins/google-analytics-for-wordpress/assets/css/A.frontend.min.css,qver=7.16.1.pagespeed.cf.EwuLFDn4Lq.css
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.main.min.css,qver=3.7.4.pagespeed.cf.7_4OumCqVs.css
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.font-awesome.min.css,qver=3.7.4.pagespeed.cf.OvW0GmWfVe.css
Allowed
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
Allowed
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery-migrate.min.js,qver=3.3.2.pagespeed.jm.Ws-UgblvVg.js
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/libs/jquery.flexslider.min.js,qver=3.7.4.pagespeed.ce.LA3M-6Qd69.js
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2019/07/xHeader-Image-AR.jpg.pagespeed.ic.c1_k64Q0Js.webp
Allowed
http://www.mofa.gov.iq/wp-content,_plugins,_pdf-viewer-block,_public,_js,_pdf-viewer-block.js,qver==5.6.2+wp-includes,_js,_underscore.min.js,qver==1.8.3.pagespeed.jc.bQNP40F31e.js
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
Allowed
http://www.mofa.gov.iq/wp-includes/js/wp-emoji-release.min.js?ver=5.6.2
Allowed
http://fonts.gstatic.com/s/sourcesanspro/v14/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2
Allowed
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu3cOWxw.woff2
Allowed
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdu3cOWxw.woff2
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-720x340.jpeg.pagespeed.ic.sDUmhgWSP5.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xIMG-20210331-WA0012-1-720x340.jpg.pagespeed.ic.EQiekG_Imm.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-720x340.jpeg.pagespeed.ic.nSqft41m_m.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x1-720x340.jpg.pagespeed.ic.wKspkvD5o5.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-720x340.jpg.pagespeed.ic.d8lrQQamTv.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x9C3732A4-B6E2-4A94-9905-01DCD313C151-720x340.jpeg.pagespeed.ic.K0Kd6CyXQE.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-80x80.jpeg.pagespeed.ic.LZDTBaBeC1.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xIMG-20210331-WA0012-1-80x80.jpg.pagespeed.ic.UUSBRP5kjf.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-80x80.jpeg.pagespeed.ic.aoh8oQ6YyH.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x1-80x80.jpg.pagespeed.ic.FucmGIUXTM.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-80x80.jpg.pagespeed.ic.NnA5_AREE4.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xC86BE556-F9A2-4B35-8277-77B5DA16456A-80x80.jpeg.pagespeed.ic.8fmVCRwwQb.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/03/x071754E3-B53F-4383-A87D-72D815B08B12-80x80.jpeg.pagespeed.ic.EjNqPh3YAb.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_0295-80x80.jpg.pagespeed.ic.M-oglodBLh.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xphoto_2021-03-20_19-55-36-80x80.jpg.pagespeed.ic.-BcVrMUFlg.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_0609-80x80.jpg.pagespeed.ic.Pt0z9vjJuy.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_1232-720x340.jpg.pagespeed.ic.m31Im30YVD.webp
Allowed
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mofa.gov.iq. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mofa.gov.iq on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
27

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of mofa.gov.iq. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mofa.gov.iq on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 71
Performance 50
Accessibility 94
Best Practices 93
SEO 84
Progressive Web App 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://www.mofa.gov.iq/
Updated: 1st April, 2021

3.01 seconds
First Contentful Paint (FCP)
1%
74%
25%

0.03 seconds
First Input Delay (FID)
96%
3%
1%

Simulate loading on mobile
50

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for mofa.gov.iq. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 200 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Estimated Input Latency — 30 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive mofa.gov.iq as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mofa.gov.iq/
http/1.1
0
559.57899987698
340
0
302
text/html
http://www.mofa.gov.iq/
http/1.1
560.23099995218
1881.9629999343
18430
111008
200
text/html
Document
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-brands-400.woff2?v=5.15.2
http/1.1
1903.349999804
2809.8989999853
78803
78472
200
font/woff2
Font
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-regular-400.woff2?v=5.15.2
http/1.1
1903.5739998799
2364.0099999029
13918
13588
200
font/woff2
Font
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-solid-900.woff2?v=5.15.2
http/1.1
1903.7059999537
2828.985999804
80583
80252
200
font/woff2
Font
http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,300italic,300,400italic,600&subset=latin,latin-ext
http/1.1
1915.0549999904
1939.9439999834
1418
11179
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-includes/css/dist/block-library/style-rtl.min.css,qver=5.6.2.pagespeed.ce.3h8fyPnXJ_.css
http/1.1
1916.3889999036
2389.1939998139
8249
51161
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-content/plugins/google-analytics-for-wordpress/assets/css/A.frontend.min.css,qver=7.16.1.pagespeed.cf.EwuLFDn4Lq.css
http/1.1
1916.537999874
2164.1129998025
1237
7694
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/main.min.css?ver=3.7.4
http/1.1
1916.6419999674
2601.1079999153
18512
95231
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.font-awesome.min.css,qver=3.7.4.pagespeed.cf.OvW0GmWfVe.css
http/1.1
1916.7559999041
2389.8459998891
13034
59347
200
text/css
Stylesheet
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
http/1.1
1916.8829999398
2620.1139998157
31278
89410
200
application/javascript
Script
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery-migrate.min.js,qver=3.3.2.pagespeed.jm.Ws-UgblvVg.js
http/1.1
1916.9969998766
2380.6439999025
4557
11126
200
application/javascript
Script
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/libs/jquery.flexslider.min.js,qver=3.7.4.pagespeed.ce.LA3M-6Qd69.js
http/1.1
2660.0639999378
2894.9199998751
7084
23103
200
application/javascript
Script
http://www.mofa.gov.iq/wp-content/uploads/2019/07/xHeader-Image-AR-1024x176.jpg.pagespeed.ic.wj4BWzaxaT.webp
http/1.1
2660.7209998183
5347.781999968
18971
18484
200
image/jpeg
Image
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
http/1.1
2660.9249999747
4985.3739999235
305689
305385
200
image/jpeg
Image
http://www.mofa.gov.iq/wp-content,_plugins,_pdf-viewer-block,_public,_js,_pdf-viewer-block.js,qver==5.6.2+wp-includes,_js,_underscore.min.js,qver==1.8.3.pagespeed.jc.bQNP40F31e.js
http/1.1
2659.8869999871
2895.3849999234
6486
17148
200
application/javascript
Script
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
http/1.1
2661.1949999351
3126.1679998133
21369
75631
200
application/javascript
Script
http://www.mofa.gov.iq/wp-includes/js/wp-emoji-release.min.js?ver=5.6.2
http/1.1
2661.3249999937
2895.7409998402
5004
14110
200
application/javascript
Script
http://fonts.gstatic.com/s/sourcesanspro/v14/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2
http/1.1
2718.2459998876
2725.6439998746
13715
13324
200
font/woff2
Font
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu3cOWxw.woff2
http/1.1
2732.0649998728
2736.8879998103
13499
13108
200
font/woff2
Font
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdu3cOWxw.woff2
http/1.1
2736.735999817
2746.3199999183
13615
13224
200
font/woff2
Font
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-720x340.jpeg.pagespeed.ic.j3YtokexRJ.webp
http/1.1
2937.2739999089
3412.0779999066
37980
37468
200
image/jpeg
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xIMG-20210331-WA0012-1-720x340.jpg.pagespeed.ic.7Db7Sokl56.webp
http/1.1
2937.6459999476
3192.7310000174
31437
30945
200
image/jpeg
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-720x340.jpeg.pagespeed.ic.w0u2i6wjBS.webp
http/1.1
2937.7829998266
3408.7679998484
45984
45461
200
image/jpeg
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x1-720x340.jpg.pagespeed.ic.eEo989QMQ5.webp
http/1.1
2937.9179999232
3413.8350000139
36745
36273
200
image/jpeg
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-720x340.jpg.pagespeed.ic.2fb0UaCAOy.webp
http/1.1
2938.0429999437
3648.4759999439
45157
44678
200
image/jpeg
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x9C3732A4-B6E2-4A94-9905-01DCD313C151-720x340.jpeg.pagespeed.ic.dj7wVla2GY.webp
http/1.1
2938.2119998336
3206.4669998363
51185
50677
200
image/jpeg
Image
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_1232-720x340.jpg.pagespeed.ic.jau5ICGP3A.webp
http/1.1
3423.6209997907
3723.8319998141
51771
51292
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1915.395
9.467
1974.343
75.102
2630.736
6.378
2661.104
43.003
2704.122
258.035
2973.907
44.354
3018.958
12.136
3031.111
8.871
3040.275
13.773
3054.817
55.773
3162.568
16.873
3180.435
56.253
3236.714
16.97
3280.262
51.804
3332.082
9.218
3416.833
26.252
3443.099
8.75
3454.487
7.672
3499.903
6.14
5380.925
5.675
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Mofa.gov.iq should consider serving more appropriate-sized images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mofa.gov.iq should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mofa.gov.iq should consider minifying JS files.
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Mofa.gov.iq should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mofa.gov.iq/
630
http://www.mofa.gov.iq/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mofa.gov.iq should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_1232-720x340.jpg.pagespeed.ic.jau5ICGP3A.webp
0

Diagnostics

Avoids enormous network payloads — Total size was 953 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
305689
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-solid-900.woff2?v=5.15.2
80583
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-brands-400.woff2?v=5.15.2
78803
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_1232-720x340.jpg.pagespeed.ic.jau5ICGP3A.webp
51771
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x9C3732A4-B6E2-4A94-9905-01DCD313C151-720x340.jpeg.pagespeed.ic.dj7wVla2GY.webp
51185
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-720x340.jpeg.pagespeed.ic.w0u2i6wjBS.webp
45984
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-720x340.jpg.pagespeed.ic.2fb0UaCAOy.webp
45157
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-720x340.jpeg.pagespeed.ic.j3YtokexRJ.webp
37980
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x1-720x340.jpg.pagespeed.ic.eEo989QMQ5.webp
36745
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xIMG-20210331-WA0012-1-720x340.jpg.pagespeed.ic.7Db7Sokl56.webp
31437
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mofa.gov.iq should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://www.mofa.gov.iq/
2179.964
364.684
11.672
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
1068.376
584.22
7.924
Unattributable
255.928
4.228
0.708
Keep request counts low and transfer sizes small — 28 requests • 953 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
28
976050
Image
9
624919
Font
6
214133
Script
6
75778
Stylesheet
5
42450
Document
1
18430
Other
1
340
Media
0
0
Third-party
4
42247
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
42247
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.34880182054308
5.7418823242187E-5
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 11 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://www.mofa.gov.iq/
1725
516
http://www.mofa.gov.iq/
1425
300
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
5580
172
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
8647
113
http://www.mofa.gov.iq/
2379
112
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
8833
104
http://www.mofa.gov.iq/
2241
89
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
8760
68
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
8580
67
http://www.mofa.gov.iq/wp-content,_plugins,_pdf-viewer-block,_public,_js,_pdf-viewer-block.js,qver==5.6.2+wp-includes,_js,_underscore.min.js,qver==1.8.3.pagespeed.jc.bQNP40F31e.js
8250
55
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
8937
53
Avoid non-composited animations — 5 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element
a
img
img

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 3.0 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 6.5 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 4.1 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 170 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.

Opportunities

Remove unused CSS — Potential savings of 26 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mofa.gov.iq should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/main.min.css?ver=3.7.4
18512
14147
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.font-awesome.min.css,qver=3.7.4.pagespeed.cf.OvW0GmWfVe.css
13034
12883
Efficiently encode images — Potential savings of 195 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
305385
200175
Avoid serving legacy JavaScript to modern browsers — Potential savings of 9 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
9461

Diagnostics

Avoid an excessive DOM size — 876 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
876
Maximum DOM Depth
img
17
Maximum Child Elements
89
Minimize main-thread work — 3.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
1518.168
Script Evaluation
999.648
Other
539.952
Rendering
407.056
Parse HTML & CSS
142.388
Script Parsing & Compilation
45.152

Metrics

Speed Index — 8.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 7.0 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.349
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 1,170 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mofa.gov.iq should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,300italic,300,400italic,600&subset=latin,latin-ext
1418
630
http://www.mofa.gov.iq/wp-includes/css/dist/block-library/style-rtl.min.css,qver=5.6.2.pagespeed.ce.3h8fyPnXJ_.css
8249
480
http://www.mofa.gov.iq/wp-content/plugins/google-analytics-for-wordpress/assets/css/A.frontend.min.css,qver=7.16.1.pagespeed.cf.EwuLFDn4Lq.css
1237
330
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/main.min.css?ver=3.7.4
18512
780
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.font-awesome.min.css,qver=3.7.4.pagespeed.cf.OvW0GmWfVe.css
13034
780
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
31278
1230
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery-migrate.min.js,qver=3.3.2.pagespeed.jm.Ws-UgblvVg.js
4557
480
Defer offscreen images — Potential savings of 298 KiB
Time to Interactive can be slowed down by resources on the page. Mofa.gov.iq should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
305385
305385
Serve images in next-gen formats — Potential savings of 295 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
305385
238141
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xIMG-20210331-WA0012-1-720x340.jpg.pagespeed.ic.7Db7Sokl56.webp
30945
11813
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-720x340.jpg.pagespeed.ic.2fb0UaCAOy.webp
44678
11394
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-720x340.jpeg.pagespeed.ic.j3YtokexRJ.webp
37468
11198
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_1232-720x340.jpg.pagespeed.ic.jau5ICGP3A.webp
51292
10518
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x1-720x340.jpg.pagespeed.ic.eEo989QMQ5.webp
36273
10269
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-720x340.jpeg.pagespeed.ic.w0u2i6wjBS.webp
45461
9203
Reduce initial server response time — Root document took 1,320 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://www.mofa.gov.iq/
1322.729

Diagnostics

Serve static assets with an efficient cache policy — 7 resources found
Mofa.gov.iq can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
0
305689
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-solid-900.woff2?v=5.15.2
0
80583
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-brands-400.woff2?v=5.15.2
0
78803
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-regular-400.woff2?v=5.15.2
0
13918
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/main.min.css?ver=3.7.4
109000
18512
http://www.mofa.gov.iq/wp-includes/js/wp-emoji-release.min.js?ver=5.6.2
133000
5004
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
161000
21369
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
http://fonts.gstatic.com/s/sourcesanspro/v14/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2
7.3979999870062
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu3cOWxw.woff2
4.8229999374598
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdu3cOWxw.woff2
9.584000101313
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.mofa.gov.iq/wp-content/uploads/2020/06/DSC_0849-4.jpg
img

Other

First Contentful Paint (3G) — 6150 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
94

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mofa.gov.iq. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Mofa.gov.iq may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-hidden="true"]` elements contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
93

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that mofa.gov.iq should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Underscore
1.8.3
FlexSlider
WordPress
5.6.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 27 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://mofa.gov.iq/
Allowed
http://www.mofa.gov.iq/
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-brands-400.woff2?v=5.15.2
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-regular-400.woff2?v=5.15.2
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/webfonts/fa-solid-900.woff2?v=5.15.2
Allowed
http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,300italic,300,400italic,600&subset=latin,latin-ext
Allowed
http://www.mofa.gov.iq/wp-includes/css/dist/block-library/style-rtl.min.css,qver=5.6.2.pagespeed.ce.3h8fyPnXJ_.css
Allowed
http://www.mofa.gov.iq/wp-content/plugins/google-analytics-for-wordpress/assets/css/A.frontend.min.css,qver=7.16.1.pagespeed.cf.EwuLFDn4Lq.css
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/main.min.css?ver=3.7.4
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/css/A.font-awesome.min.css,qver=3.7.4.pagespeed.cf.OvW0GmWfVe.css
Allowed
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js
Allowed
http://www.mofa.gov.iq/wp-includes/js/jquery/jquery-migrate.min.js,qver=3.3.2.pagespeed.jm.Ws-UgblvVg.js
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/libs/jquery.flexslider.min.js,qver=3.7.4.pagespeed.ce.LA3M-6Qd69.js
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2019/07/xHeader-Image-AR-1024x176.jpg.pagespeed.ic.wj4BWzaxaT.webp
Allowed
http://www.mofa.gov.iq/wp-content,_plugins,_pdf-viewer-block,_public,_js,_pdf-viewer-block.js,qver==5.6.2+wp-includes,_js,_underscore.min.js,qver==1.8.3.pagespeed.jc.bQNP40F31e.js
Allowed
http://www.mofa.gov.iq/wp-content/themes/hueman/assets/front/js/scripts.min.js?ver=3.7.4
Allowed
http://www.mofa.gov.iq/wp-includes/js/wp-emoji-release.min.js?ver=5.6.2
Allowed
http://fonts.gstatic.com/s/sourcesanspro/v14/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2
Allowed
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu3cOWxw.woff2
Allowed
http://fonts.gstatic.com/s/sourcesanspro/v14/6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdu3cOWxw.woff2
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-31-at-11.22.30-PM-720x340.jpeg.pagespeed.ic.j3YtokexRJ.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xIMG-20210331-WA0012-1-720x340.jpg.pagespeed.ic.7Db7Sokl56.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xWhatsApp-Image-2021-03-30-at-14.48.45-1-1152x1536-1-720x340.jpeg.pagespeed.ic.w0u2i6wjBS.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x1-720x340.jpg.pagespeed.ic.eEo989QMQ5.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/xDSC_2432-720x340.jpg.pagespeed.ic.2fb0UaCAOy.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/04/x9C3732A4-B6E2-4A94-9905-01DCD313C151-720x340.jpeg.pagespeed.ic.dj7wVla2GY.webp
Allowed
http://www.mofa.gov.iq/wp-content/uploads/2021/03/xDSC_1232-720x340.jpg.pagespeed.ic.jau5ICGP3A.webp
Allowed
84

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mofa.gov.iq. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mofa.gov.iq on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 83% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
2
20x2
img
3
20x2
img
4
20x2
img
5
20x2
img
1
20x2
img
62x15
62x15
62x15
62x15
62x15
94x18
72x18
72x18
72x18
72x18

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
33

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of mofa.gov.iq. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mofa.gov.iq on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 13.67.50.87
Continent: Asia
Country: Singapore
Singapore Flag
Region:
City: Singapore
Longitude: 103.8547
Latitude: 1.2929
Currencies: SGD
Languages: Mandarin
English
Malay
Tamil

Web Hosting Provider

Name IP Address
Microsoft Corporation
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 4/5 (0 reviews)
WOT Trustworthiness: 80/100
WOT Child Safety: 100/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: mofa.gov.iq
Issued By: R3
Valid From: 20th February, 2021
Valid To: 21st May, 2021
Subject: CN = mofa.gov.iq
Hash: 7ad30f5f
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x0404EEA68DBC91B5F0BE406BC102CF470DE4
Serial Number (Hex): 0404EEA68DBC91B5F0BE406BC102CF470DE4
Valid From: 20th February, 2024
Valid To: 21st May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
Timestamp : Feb 20 21:38:34.359 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:1E:82:54:96:93:57:96:CD:0F:FB:54:2B:
63:6E:12:11:FB:72:42:F6:CE:A7:70:C5:2A:05:16:47:
81:88:BB:0D:02:20:62:81:62:4C:28:0A:2A:C2:2A:21:
CE:A6:C8:C6:28:0D:5C:77:F3:76:D7:A1:44:E5:67:08:
6B:2D:FD:52:32:0A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Feb 20 21:38:34.337 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:4E:CF:46:F5:C8:DD:BB:F6:7D:6A:74:92:
B2:DF:A6:94:F6:1F:90:EF:C9:FA:2F:46:FC:92:8D:B6:
F7:3E:C6:64:02:20:67:CD:70:2C:82:0F:A2:69:F6:AA:
91:02:61:74:4B:8B:14:5F:01:94:12:A5:A1:CB:90:F6:
F6:C9:51:EB:79:B2
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.mofa.gov.iq
DNS:mofa.gov.iq
Technical

DNS Lookup

A Records

Host IP Address Class TTL
mofa.gov.iq. 13.67.50.87 IN 3599

NS Records

Host Nameserver Class TTL
mofa.gov.iq. ns1-03.azure-dns.com. IN 21599
mofa.gov.iq. ns2-03.azure-dns.net. IN 21599
mofa.gov.iq. ns3-03.azure-dns.org. IN 21599
mofa.gov.iq. ns4-03.azure-dns.info. IN 21599

MX Records

Priority Host Server Class TTL
1 mofa.gov.iq. mail.mofa.gov.iq. IN 3599
2 mofa.gov.iq. mail2.mofa.gov.iq. IN 3599
3 mofa.gov.iq. mail3.mofa.gov.iq. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
mofa.gov.iq. ns1-03.azure-dns.com. azuredns-hostmaster.microsoft.com. 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 1st April, 2021
Server: Apache
Cache-Control: max-age=0, no-cache
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/7.2.16
Link: <http://www.mofa.gov.iq/wp-json/>; rel="https://api.w.org/"
Set-Cookie: *
X-Frame-Options: SAMEORIGIN

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1-03.azure-dns.com
ns2-03.azure-dns.net
ns3-03.azure-dns.org
ns4-03.azure-dns.info
Full Whois:

Nameservers

Name IP Address
ns1-03.azure-dns.com 13.107.236.3
ns2-03.azure-dns.net 150.171.21.3
ns3-03.azure-dns.org 204.14.183.3
ns4-03.azure-dns.info 208.84.5.3
Related

Subdomains

Domain Subdomain
mail
mail2
services

Similar Sites

Domain Valuation Snoop Score
0/5
0/5
$10 USD 1/5
$1,010 USD 1/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5
0/5

Sites hosted on the same IP address