yemen.com

yemen.com may not be SSL secured

Free website and domain report on yemen.com

Last Updated: 20th June, 2022 Update Now
Overview

Snoop Summary for yemen.com

This is a free and comprehensive report about yemen.com. Yemen.com is hosted in Groningen, Groningen in Netherlands on a server with an IP address of 34.90.25.136, where EUR is the local currency and the local language is Dutch. Our records indicate that yemen.com is privately registered by Contact Privacy Inc. Customer 0156492423. Yemen.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If yemen.com was to be sold it would possibly be worth $891 USD (based on the daily revenue potential of the website over a 24 month period). Yemen.com is somewhat popular with an estimated 423 daily unique visitors. This report was last updated 20th June, 2022.

About yemen.com

Site Preview: yemen.com yemen.com
Title: Home
Description:
Keywords and Tags: parked domain
Related Terms: yemen
Fav Icon:
Age: Over 28 years old
Domain Created: 21st February, 1996
Domain Updated: 16th March, 2022
Domain Expires: 22nd February, 2029
Review

Snoop Score

1/5

Valuation

$891 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,441,805
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: 423
Monthly Visitors: 12,888
Yearly Visitors: 154,549
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $37 USD
Yearly Revenue: $440 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: yemen.com 9
Domain Name: yemen 5
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 78
Performance 94
Accessibility 100
Best Practices 83
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
94

Performance

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

Metrics

Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
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://yemen.com/
http/1.1
0
245.89800008107
367
0
301
text/html
http://yemen.com/index.html
http/1.1
246.30500003695
488.06000000332
3274
14534
200
text/html
Document
http://yemen.com/gdpr/gdprscript.js?buildTime=1648501434&hasRemindMe=true&stealth=false
http/1.1
497.85100005101
664.24299997743
501
227
200
text/javascript
Script
http://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
http/1.1
498.15600004513
526.24999999534
30353
214956
200
text/css
Stylesheet
http://cdn2.editmysite.com/css/old/fancybox.css?1583186984
http/1.1
498.49300005008
560.00400008634
1820
3911
200
text/css
Stylesheet
http://cdn2.editmysite.com/css/social-icons.css?buildtime=1583186984
http/1.1
498.68100008462
528.64799997769
2243
13081
200
text/css
Stylesheet
http://yemen.com/files/main_style.css?1583335426
http/1.1
498.77100007143
751.65200000629
9510
75971
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Josefin+Sans:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
http/1.1
498.91500000376
516.03100006469
1172
6384
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Cardo:400,700,400italic&subset=latin,latin-ext
http/1.1
499.14099997841
512.45799998287
1119
3415
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Catamaran:400,300,200,700&subset=latin,latin-ext
http/1.1
499.55599999521
512.89100002032
1106
4352
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Roboto:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
http/1.1
499.792000046
517.5969999982
1498
12310
200
text/css
Stylesheet
http://cdn2.editmysite.com/fonts/Aller/font.css?2
http/1.1
500.15700003132
514.38599999528
727
162
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic&subset=latin,latin-ext
http/1.1
500.42599998415
519.28000000771
1248
6166
200
text/css
Stylesheet
http://yemen.com/files/templateArtifacts.js?1583335426
http/1.1
500.56100008078
789.68799998984
1942
7160
200
application/javascript
Script
https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js
h2
500.83300005645
507.43900006637
34672
93636
200
text/javascript
Script
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
http/1.1
501.09500007238
546.91899998579
33270
180544
200
application/javascript
Script
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
http/1.1
501.41800008714
538.75100007281
147018
477188
200
application/javascript
Script
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
http/1.1
501.63499999326
533.84599997662
33270
180544
200
application/javascript
Script
http://cdn2.editmysite.com/js/site/theme-plugins.js?buildTime=1648501434
http/1.1
501.88600004185
518.35600007325
4363
12622
200
application/javascript
Script
http://yemen.com/files/theme/plugins.js?1557172909
http/1.1
502.09299998824
840.44000005815
17853
76439
200
application/javascript
Script
http://yemen.com/files/theme/custom.js?1557172909
http/1.1
502.30100005865
742.6090000663
3307
12557
200
application/javascript
Script
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
http/1.1
503.57400008943
575.57700003963
159592
533896
200
application/javascript
Script
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
http/1.1
879.60700003896
899.89900006913
116526
115632
200
image/jpeg
Image
http://fonts.gstatic.com/s/josefinsans/v24/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
http/1.1
880.03700005356
884.53999999911
27392
26632
200
font/woff2
Font
http://yemen.com/ajax/api/JsonRPC/CustomerAccounts/?CustomerAccounts[CustomerAccounts::getAccountDetails]
http/1.1
1010.4080000892
1471.5550000547
582
348
200
application/json
XHR
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)
533.87
5.927
540.299
5.447
708.649
9.14
834.313
87.365
921.694
5.22
931.414
117.049
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Yemen.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Yemen.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Yemen.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 9 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Yemen.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://yemen.com/files/theme/plugins.js?1557172909
17853
9044
Reduce unused CSS — Potential savings of 30 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Yemen.com 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://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
30353
30298
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 48 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
115632
49461.7
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.
Initial server response time was short — Root document took 240 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://yemen.com/index.html
242.75
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Yemen.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://yemen.com/
190
http://yemen.com/index.html
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Yemen.com 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 0 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://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
50
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 620 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
159592
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
147018
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
116526
https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js
34672
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
33270
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
33270
http://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
30353
http://fonts.gstatic.com/s/josefinsans/v24/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
27392
http://yemen.com/files/theme/plugins.js?1557172909
17853
http://yemen.com/files/main_style.css?1583335426
9510
Avoids an excessive DOM size — 40 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
40
Maximum DOM Depth
12
Maximum Child Elements
6
Avoid chaining critical requests — 20 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Yemen.com 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.1 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://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
87.195
78.673
8.178
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
53.786
38.234
7.825
Minimizes main-thread work — 0.3 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
159.736
Other
39.85
Parse HTML & CSS
28.547
Script Parsing & Compilation
27.191
Style & Layout
16.116
Rendering
2.048
Keep request counts low and transfer sizes small — 25 requests • 620 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
25
634725
Script
10
435788
Image
1
116526
Stylesheet
10
50796
Font
1
27392
Document
1
3274
Other
2
949
Media
0
0
Third-party
17
597389
Minimize third-party usage — Third-party code blocked the main thread for 20 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)
529182
24.464
34672
0
33535
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
 
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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 — 1 long task 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://yemen.com/files/theme/plugins.js?1557172909
1204
59
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 yemen.com on mobile screens.
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.

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 — 1.1 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.3 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 530 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Yemen.com 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://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
30353
430
http://cdn2.editmysite.com/css/old/fancybox.css?1583186984
1820
190
http://cdn2.editmysite.com/css/social-icons.css?buildtime=1583186984
2243
190
http://yemen.com/files/main_style.css?1583335426
9510
150
http://fonts.googleapis.com/css?family=Josefin+Sans:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
1172
190
http://fonts.googleapis.com/css?family=Cardo:400,700,400italic&subset=latin,latin-ext
1119
190
http://fonts.googleapis.com/css?family=Catamaran:400,300,200,700&subset=latin,latin-ext
1106
190
http://fonts.googleapis.com/css?family=Roboto:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
1498
190
http://cdn2.editmysite.com/fonts/Aller/font.css?2
727
190
http://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic&subset=latin,latin-ext
1248
190
http://yemen.com/gdpr/gdprscript.js?buildTime=1648501434&hasRemindMe=true&stealth=false
501
110
http://yemen.com/files/templateArtifacts.js?1583335426
1942
110
https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js
34672
390
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
33270
310
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
147018
590
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
33270
310
http://cdn2.editmysite.com/js/site/theme-plugins.js?buildTime=1648501434
4363
110
Reduce unused JavaScript — Potential savings of 201 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
147018
104535
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
159592
101467
Serve static assets with an efficient cache policy — 11 resources found
Yemen.com 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)
http://yemen.com/gdpr/gdprscript.js?buildTime=1648501434&hasRemindMe=true&stealth=false
0
501
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
86400000
116526
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
1209600000
159592
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
1209600000
147018
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
1209600000
33270
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
1209600000
33270
http://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
1209600000
30353
http://cdn2.editmysite.com/js/site/theme-plugins.js?buildTime=1648501434
1209600000
4363
http://cdn2.editmysite.com/css/social-icons.css?buildtime=1583186984
1209600000
2243
http://cdn2.editmysite.com/css/old/fancybox.css?1583186984
1209600000
1820
http://cdn2.editmysite.com/fonts/Aller/font.css?2
1209600000
727

Other

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/josefinsans/v24/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
4.5029999455437
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of yemen.com. 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-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
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.
Links 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.
`<object>` elements have alternate 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.

Contrast

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

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"]`
Yemen.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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.
83

Best Practices

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

Audits

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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.3.5
jQuery
1.8.3
Underscore
1.8.3
Mustache
2.1.3
Hammer.js
2.0.4
core-js
core-js-global@2.6.12
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 — 24 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://yemen.com/
Allowed
http://yemen.com/index.html
Allowed
http://yemen.com/gdpr/gdprscript.js?buildTime=1648501434&hasRemindMe=true&stealth=false
Allowed
http://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
Allowed
http://cdn2.editmysite.com/css/old/fancybox.css?1583186984
Allowed
http://cdn2.editmysite.com/css/social-icons.css?buildtime=1583186984
Allowed
http://yemen.com/files/main_style.css?1583335426
Allowed
http://fonts.googleapis.com/css?family=Josefin+Sans:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
Allowed
http://fonts.googleapis.com/css?family=Cardo:400,700,400italic&subset=latin,latin-ext
Allowed
http://fonts.googleapis.com/css?family=Catamaran:400,300,200,700&subset=latin,latin-ext
Allowed
http://fonts.googleapis.com/css?family=Roboto:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
Allowed
http://cdn2.editmysite.com/fonts/Aller/font.css?2
Allowed
http://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic&subset=latin,latin-ext
Allowed
http://yemen.com/files/templateArtifacts.js?1583335426
Allowed
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
Allowed
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
Allowed
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
Allowed
http://cdn2.editmysite.com/js/site/theme-plugins.js?buildTime=1648501434
Allowed
http://yemen.com/files/theme/plugins.js?1557172909
Allowed
http://yemen.com/files/theme/custom.js?1557172909
Allowed
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
Allowed
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
Allowed
http://fonts.gstatic.com/s/josefinsans/v24/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
Allowed
http://yemen.com/ajax/api/JsonRPC/CustomerAccounts/?CustomerAccounts[CustomerAccounts::getAccountDetails]
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 13 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
5
Medium
6
Medium
1
Medium
1
Medium
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for yemen.com. 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 yemen.com 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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered 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.

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.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of yemen.com. 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 yemen.com on mobile screens.

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.
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
Does not provide 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.
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) 73
Performance 60
Accessibility 100
Best Practices 83
SEO 92
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
60

Performance

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

Metrics

Total Blocking Time — 180 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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Yemen.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Yemen.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Yemen.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 9 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Yemen.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://yemen.com/files/theme/plugins.js?1557172909
17853
9044
Reduce unused CSS — Potential savings of 30 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Yemen.com 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://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
30353
30280
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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.
Initial server response time was short — Root document took 110 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://yemen.com/index.html
106.817
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Yemen.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://yemen.com/
630
http://yemen.com/index.html
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Yemen.com 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 0 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://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
50
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 620 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
159592
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
147018
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
116526
https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js
34672
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
33270
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
33269
http://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
30353
http://fonts.gstatic.com/s/josefinsans/v24/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
27392
http://yemen.com/files/theme/plugins.js?1557172909
17853
http://yemen.com/files/main_style.css?1583335426
9510
Avoids an excessive DOM size — 40 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
40
Maximum DOM Depth
12
Maximum Child Elements
6
Avoid chaining critical requests — 20 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Yemen.com 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.7 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://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
353.548
320.596
31.356
http://yemen.com/index.html
224.812
13.728
8.288
Unattributable
161.1
12.184
0.976
https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js
156.628
118.484
6.512
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
154.98
126.536
28.284
Minimizes main-thread work — 1.1 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
623.348
Other
174.612
Parse HTML & CSS
114.704
Script Parsing & Compilation
103.328
Style & Layout
76.384
Garbage Collection
12.736
Rendering
8.624
Keep request counts low and transfer sizes small — 25 requests • 620 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
25
634815
Script
10
435787
Image
1
116526
Stylesheet
10
50882
Font
1
27392
Document
1
3274
Other
2
954
Media
0
0
Third-party
17
597474
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
 
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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 — 2 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://yemen.com/files/templateArtifacts.js?1583335426
5220
272
http://yemen.com/files/theme/plugins.js?1557172909
5492
239
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 yemen.com on mobile screens.
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.

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.

Audits

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://yemen.com/
http/1.1
0
159.51999998651
371
0
301
text/html
http://yemen.com/index.html
http/1.1
159.92200002074
265.7439999748
3274
14534
200
text/html
Document
http://yemen.com/gdpr/gdprscript.js?buildTime=1648501434&hasRemindMe=true&stealth=false
http/1.1
278.76000013202
476.43000003882
501
227
200
text/javascript
Script
http://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
http/1.1
279.14300002158
309.35500003397
30353
214956
200
text/css
Stylesheet
http://cdn2.editmysite.com/css/old/fancybox.css?1583186984
http/1.1
279.4119999744
296.03100009263
1819
3911
200
text/css
Stylesheet
http://cdn2.editmysite.com/css/social-icons.css?buildtime=1583186984
http/1.1
279.74199992605
309.9279999733
2243
13081
200
text/css
Stylesheet
http://yemen.com/files/main_style.css?1583335426
http/1.1
280.22800013423
399.35100008734
9510
75971
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Josefin+Sans:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
http/1.1
280.40700010024
300.8320000954
1172
6384
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Cardo:400,700,400italic&subset=latin,latin-ext
http/1.1
280.84699995816
301.77500005811
1119
3415
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Catamaran:400,300,200,700&subset=latin,latin-ext
http/1.1
281.38800011948
297.87000012584
1106
4352
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Roboto:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
http/1.1
281.71000001021
301.37200001627
1585
15348
200
text/css
Stylesheet
http://cdn2.editmysite.com/fonts/Aller/font.css?2
http/1.1
281.85299993493
297.45299997739
727
162
200
text/css
Stylesheet
http://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic&subset=latin,latin-ext
http/1.1
282.1919999551
328.76199996099
1248
6166
200
text/css
Stylesheet
http://yemen.com/files/templateArtifacts.js?1583335426
http/1.1
282.30600012466
520.93499992043
1942
7160
200
application/javascript
Script
https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js
h2
282.64599991962
292.69000003114
34672
93636
200
text/javascript
Script
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
http/1.1
283.02700002678
305.30100013129
33269
180544
200
application/javascript
Script
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
http/1.1
283.47999998368
340.01799998805
147018
477188
200
application/javascript
Script
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
http/1.1
283.8880000636
320.09500009008
33270
180544
200
application/javascript
Script
http://cdn2.editmysite.com/js/site/theme-plugins.js?buildTime=1648501434
http/1.1
284.23300012946
303.30000002868
4363
12622
200
application/javascript
Script
http://yemen.com/files/theme/plugins.js?1557172909
http/1.1
284.65300006792
506.54400000349
17853
76439
200
application/javascript
Script
http://yemen.com/files/theme/custom.js?1557172909
http/1.1
285.81700008363
392.31200003996
3307
12557
200
application/javascript
Script
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
http/1.1
287.20899997279
352.03299997374
159592
533896
200
application/javascript
Script
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
http/1.1
598.54299994186
639.0019999817
116526
115632
200
image/jpeg
Image
http://fonts.gstatic.com/s/josefinsans/v24/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
http/1.1
599.30699993856
603.49799995311
27392
26632
200
font/woff2
Font
http://yemen.com/ajax/api/JsonRPC/CustomerAccounts/?CustomerAccounts[CustomerAccounts::getAccountDetails]
http/1.1
735.05900008604
1202.9689999763
583
348
200
application/json
XHR
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)
310.701
8.289
319.728
6.791
519.688
11.402
564.263
67.939
632.22
13.334
648.991
119.424
777.345
5.348
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Time to Interactive — 5.5 s
The time taken for the page to become fully interactive.
Speed Index — 5.3 s
The time taken for the page contents to be visibly populated.

Other

Serve images in next-gen formats — Potential savings of 48 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
115632
49461.7
Serve static assets with an efficient cache policy — 11 resources found
Yemen.com 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)
http://yemen.com/gdpr/gdprscript.js?buildTime=1648501434&hasRemindMe=true&stealth=false
0
501
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
86400000
116526
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
1209600000
159592
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
1209600000
147018
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
1209600000
33270
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
1209600000
33269
http://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
1209600000
30353
http://cdn2.editmysite.com/js/site/theme-plugins.js?buildTime=1648501434
1209600000
4363
http://cdn2.editmysite.com/css/social-icons.css?buildtime=1583186984
1209600000
2243
http://cdn2.editmysite.com/css/old/fancybox.css?1583186984
1209600000
1819
http://cdn2.editmysite.com/fonts/Aller/font.css?2
1209600000
727

Metrics

First Contentful Paint — 5.3 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 5.7 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 270 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 5.3 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 2,940 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Yemen.com 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://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
30353
2130
http://cdn2.editmysite.com/css/old/fancybox.css?1583186984
1819
780
http://cdn2.editmysite.com/css/social-icons.css?buildtime=1583186984
2243
780
http://yemen.com/files/main_style.css?1583335426
9510
630
http://fonts.googleapis.com/css?family=Josefin+Sans:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
1172
630
http://fonts.googleapis.com/css?family=Cardo:400,700,400italic&subset=latin,latin-ext
1119
630
http://fonts.googleapis.com/css?family=Catamaran:400,300,200,700&subset=latin,latin-ext
1106
630
http://fonts.googleapis.com/css?family=Roboto:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
1585
780
http://cdn2.editmysite.com/fonts/Aller/font.css?2
727
630
http://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic&subset=latin,latin-ext
1248
630
http://yemen.com/gdpr/gdprscript.js?buildTime=1648501434&hasRemindMe=true&stealth=false
501
330
http://yemen.com/files/templateArtifacts.js?1583335426
1942
330
https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js
34672
2130
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
33269
1830
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
147018
3330
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
33270
1830
http://cdn2.editmysite.com/js/site/theme-plugins.js?buildTime=1648501434
4363
480
Reduce unused JavaScript — Potential savings of 201 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
147018
104535
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
159592
101467
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/josefinsans/v24/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
4.1910000145435
Reduce the impact of third-party code — Third-party code blocked the main thread for 340 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)
529180
319.912
34672
19.164
33622
0
First Contentful Paint (3G) — 10559 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of yemen.com. 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-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
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.
Links 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.
`<object>` elements have alternate 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.

Contrast

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

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"]`
Yemen.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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.
83

Best Practices

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

Audits

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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.3.5
jQuery
1.8.3
Underscore
1.8.3
Mustache
2.1.3
Hammer.js
2.0.4
core-js
core-js-global@2.6.12
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 — 24 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://yemen.com/
Allowed
http://yemen.com/index.html
Allowed
http://yemen.com/gdpr/gdprscript.js?buildTime=1648501434&hasRemindMe=true&stealth=false
Allowed
http://cdn2.editmysite.com/css/sites.css?buildTime=1648501434
Allowed
http://cdn2.editmysite.com/css/old/fancybox.css?1583186984
Allowed
http://cdn2.editmysite.com/css/social-icons.css?buildtime=1583186984
Allowed
http://yemen.com/files/main_style.css?1583335426
Allowed
http://fonts.googleapis.com/css?family=Josefin+Sans:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
Allowed
http://fonts.googleapis.com/css?family=Cardo:400,700,400italic&subset=latin,latin-ext
Allowed
http://fonts.googleapis.com/css?family=Catamaran:400,300,200,700&subset=latin,latin-ext
Allowed
http://fonts.googleapis.com/css?family=Roboto:400,300,300italic,700,400italic,700italic&subset=latin,latin-ext
Allowed
http://cdn2.editmysite.com/fonts/Aller/font.css?2
Allowed
http://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic&subset=latin,latin-ext
Allowed
http://yemen.com/files/templateArtifacts.js?1583335426
Allowed
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1583186984&
Allowed
http://cdn2.editmysite.com/js/site/main.js?buildTime=1648501434
Allowed
http://cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1648501434&
Allowed
http://cdn2.editmysite.com/js/site/theme-plugins.js?buildTime=1648501434
Allowed
http://yemen.com/files/theme/plugins.js?1557172909
Allowed
http://yemen.com/files/theme/custom.js?1557172909
Allowed
http://cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildTime=1648501434
Allowed
http://cdn2.editmysite.com/images/editor/theme-background/stock/Rock-Climbing.jpg
Allowed
http://fonts.gstatic.com/s/josefinsans/v24/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
Allowed
http://yemen.com/ajax/api/JsonRPC/CustomerAccounts/?CustomerAccounts[CustomerAccounts::getAccountDetails]
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 13 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
5
Medium
6
Medium
1
Medium
1
Medium
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for yemen.com. 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 yemen.com 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 — 100% 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.

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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered 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.

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.
30

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of yemen.com. 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 yemen.com on mobile screens.

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.
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
Does not provide 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.
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: 34.90.25.136
Continent: Europe
Country: Netherlands
Netherlands Flag
Region: Groningen
City: Groningen
Longitude: 6.5765
Latitude: 53.2157
Currencies: EUR
Languages: Dutch

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

Private Registration: Yes
Name: Contact Privacy Inc. Customer 0156492423
Organization: Contact Privacy Inc. Customer 0156492423
Country: CA
City: Toronto
State: ON
Post Code: M6K 3M1
Email: yemen.com@contactprivacy.com
Phone: +1.4165385457
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
TUCOWS, INC. 199.16.172.52
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
yemen.com. 34.90.25.136 IN 21600

NS Records

Host Nameserver Class TTL
yemen.com. ns1.siteground.net. IN 21600
yemen.com. ns2.siteground.net. IN 21600

MX Records

Priority Host Server Class TTL
10 yemen.com. mx10.mailspamprotection.com. IN 21600
20 yemen.com. mx20.mailspamprotection.com. IN 21600
30 yemen.com. mx30.mailspamprotection.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
yemen.com. ns1.siteground.net. root.gnldm1003.siteground.biz. 14400

TXT Records

Host Value Class TTL
yemen.com. v=spf1 IN 14400

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 20th June, 2022
Content-Type: text/html
Expires: 17th December, 2022
Cache-Control: max-age=15552000
Content-Length: 14534
Last-Modified: 29th March, 2022
Connection: keep-alive
Vary: Accept-Encoding
ETag: "6242fdd2-38c6"
Host-Header: 8441280b0c35cbc1147f8ba998a563a7
X-Proxy-Cache-Info: DT:1
Accept-Ranges: bytes

Whois Lookup

Created: 21st February, 1996
Changed: 16th March, 2022
Expires: 22nd February, 2029
Registrar: TUCOWS, INC.
Status: ok
Nameservers: ns1.siteground.net
ns2.siteground.net
Owner Name: Contact Privacy Inc. Customer 0156492423
Owner Organization: Contact Privacy Inc. Customer 0156492423
Owner Street: 96 Mowat Ave
Owner Post Code: M6K 3M1
Owner City: Toronto
Owner State: ON
Owner Country: CA
Owner Phone: +1.4165385457
Owner Email: yemen.com@contactprivacy.com
Admin Name: Contact Privacy Inc. Customer 0156492423
Admin Organization: Contact Privacy Inc. Customer 0156492423
Admin Street: 96 Mowat Ave
Admin Post Code: M6K 3M1
Admin City: Toronto
Admin State: ON
Admin Country: CA
Admin Phone: +1.4165385457
Admin Email: yemen.com@contactprivacy.com
Tech Name: Contact Privacy Inc. Customer 0156492423
Tech Organization: Contact Privacy Inc. Customer 0156492423
Tech Street: 96 Mowat Ave
Tech Post Code: M6K 3M1
Tech City: Toronto
Tech State: ON
Tech Country: CA
Tech Phone: +1.4165385457
Tech Email: yemen.com@contactprivacy.com
Full Whois: Domain Name: YEMEN.COM
Registry Domain ID: 74640_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://tucowsdomains.com
Updated Date: 2022-03-16T02:04:09
Creation Date: 1996-02-21T05:00:00
Registrar Registration Expiration Date: 2029-02-22T05:00:00
Registrar: TUCOWS, INC.
Registrar IANA ID: 69
Reseller: SiteGround Hosting Ltd.
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID:
Registrant Name: Contact Privacy Inc. Customer 0156492423
Registrant Organization: Contact Privacy Inc. Customer 0156492423
Registrant Street: 96 Mowat Ave
Registrant City: Toronto
Registrant State/Province: ON
Registrant Postal Code: M6K 3M1
Registrant Country: CA
Registrant Phone: +1.4165385457
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: yemen.com@contactprivacy.com
Registry Admin ID:
Admin Name: Contact Privacy Inc. Customer 0156492423
Admin Organization: Contact Privacy Inc. Customer 0156492423
Admin Street: 96 Mowat Ave
Admin City: Toronto
Admin State/Province: ON
Admin Postal Code: M6K 3M1
Admin Country: CA
Admin Phone: +1.4165385457
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: yemen.com@contactprivacy.com
Registry Tech ID:
Tech Name: Contact Privacy Inc. Customer 0156492423
Tech Organization: Contact Privacy Inc. Customer 0156492423
Tech Street: 96 Mowat Ave
Tech City: Toronto
Tech State/Province: ON
Tech Postal Code: M6K 3M1
Tech Country: CA
Tech Phone: +1.4165385457
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: yemen.com@contactprivacy.com
Name Server: ns1.siteground.net
Name Server: ns2.siteground.net
DNSSEC: unsigned
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
URL of the ICANN WHOIS Data Problem Reporting System: https://icann.org/wicf
>>> Last update of WHOIS database: 2022-06-20T03:24:45Z <<<

"For more information on Whois status codes, please visit https://icann.org/epp"

Registration Service Provider:
SiteGround Hosting Ltd., tucows@domains.siteground.com
+44.8008620379
This company may be contacted for domain login/passwords,
DNS/Nameserver changes, and general domain support questions.

The Data in the Tucows Registrar WHOIS database is provided to you by Tucows
for information purposes only, and may be used to assist you in obtaining
information about or related to a domain name's registration record.

Tucows makes this information available "as is," and does not guarantee its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
a) allow, enable, or otherwise support the transmission by e-mail,
telephone, or facsimile of mass, unsolicited, commercial advertising or
solicitations to entities other than the data recipient's own existing
customers; or (b) enable high volume, automated, electronic processes that
send queries or data to the systems of any Registry Operator or
ICANN-Accredited registrar, except as reasonably necessary to register
domain names or modify existing registrations.

The compilation, repackaging, dissemination or other use of this Data is
expressly prohibited without the prior written consent of Tucows.

Tucows reserves the right to terminate your access to the Tucows WHOIS
database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this
policy.

Tucows reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by these terms.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.

Nameservers

Name IP Address
ns1.siteground.net 75.2.77.104
ns2.siteground.net 99.83.229.113
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$946 USD 1/5
0/5
$10 USD
$10 USD

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$1,039 USD 1/5
$277,771 USD 3/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$767 USD 1/5
0/5
$740 USD 1/5