ida2at.com

ida2at.com is SSL secured

Free website and domain report on ida2at.com

Last Updated: 17th January, 2023 Update Now
Overview

Snoop Summary for ida2at.com

This is a free and comprehensive report about ida2at.com. Ida2at.com is hosted in United States on a server with an IP address of 104.26.7.140, where USD is the local currency and the local language is English. Ida2at.com has the potential to be earning an estimated $15 USD per day from advertising revenue. If ida2at.com was to be sold it would possibly be worth $10,702 USD (based on the daily revenue potential of the website over a 24 month period). Ida2at.com is very popular with an estimated 5,139 daily unique visitors. This report was last updated 17th January, 2023.

About ida2at.com

Site Preview: ida2at.com ida2at.com
Title: إضاءات – محتوى عربي ثري
Description: محتوى عربي ثري
Keywords and Tags: general news
Related Terms:
Fav Icon:
Age: Over 9 years old
Domain Created: 8th February, 2015
Domain Updated: 15th January, 2023
Domain Expires: 8th February, 2024
Review

Snoop Score

2/5

Valuation

$10,702 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 110,199
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: 5,139
Monthly Visitors: 156,415
Yearly Visitors: 1,875,735
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $15 USD
Monthly Revenue: $446 USD
Yearly Revenue: $5,346 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: ida2at.com 10
Domain Name: ida2at 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 7.69 seconds
Load Time Comparison: Faster than 2% of sites

PageSpeed Insights

Avg. (All Categories) 70
Performance 74
Accessibility 78
Best Practices 75
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.ida2at.com/
Updated: 17th January, 2023

1.41 seconds
First Contentful Paint (FCP)
87%
8%
5%

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

Simulate loading on desktop
74

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for ida2at.com. 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.3 s
The time taken for the page to become fully interactive.
Largest Contentful Paint — 1.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
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://ida2at.com/
http/1.1
0
106.51499999221
768
0
301
text/plain
https://ida2at.com/
http/1.1
106.9140000036
193.93200002378
794
0
301
text/plain
https://www.ida2at.com/
h2
194.4750000257
348.57199998805
23223
150601
200
text/html
Document
https://www.ida2at.com/wp-includes/css/dist/block-library/style-rtl.min.css?ver=6.0.1
h2
357.47500002617
487.78299998958
12565
88773
200
text/css
Stylesheet
https://www.ida2at.com/wp-content/themes/ida2at/assets/styles/main.css?ver=1660568599
357.34799999045
10249.559000018
0
0
-1
Stylesheet
https://www.ida2at.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
357.61000000639
10252.334000019
0
0
-1
Script
https://www.ida2at.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2
357.84700000659
10251.913000015
0
0
-1
Script
https://connect.facebook.net/ar_AR/sdk.js?ver=6.0.1
h2
359.31999998866
373.80800000392
2656
3093
200
application/x-javascript
Script
https://www.ida2at.com/wp-content/themes/ida2at/assets/scripts/vendor.min.js
358.28400001628
10251.646000019
0
0
-1
Script
https://www.ida2at.com/wp-content/themes/ida2at/assets/scripts/main.js
358.46499999752
10252.741000033
0
0
-1
Script
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
h2
10252.867000003
10310.396999994
6530
17031
200
text/javascript
Script
https://connect.facebook.net/ar_AR/sdk.js?hash=6342d0ef33034ba9dc9facaa903b525c
h2
10255.352000007
10872.895999986
89632
314360
200
application/x-javascript
Script
https://www.google-analytics.com/analytics.js
h2
10257.037999982
10261.546000023
20664
50230
200
text/javascript
Script
https://connect.facebook.net/en_US/fbevents.js
h2
10257.152000035
10278.595999989
29085
108596
200
application/x-javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=1280371940&t=pageview&_s=1&dl=https%3A%2F%2Fwww.ida2at.com%2F&ul=en-us&de=UTF-8&dt=%D8%A5%D8%B6%D8%A7%D8%A1%D8%A7%D8%AA%20%E2%80%93%20%D9%85%D8%AD%D8%AA%D9%88%D9%89%20%D8%B9%D8%B1%D8%A8%D9%8A%20%D8%AB%D8%B1%D9%8A&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAACAAI~&jid=1313694460&gjid=1575959231&cid=1287990128.1673973481&tid=UA-71912555-1&_gid=1928870082.1673973481&_r=1&_slc=1&z=512862949
h2
10363.665000012
10367.888999986
615
4
200
text/plain
XHR
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
h2
10374.635000015
10471.908000007
17201
41461
200
application/javascript
Script
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
h2
10393.267000036
10419.323000009
111245
385574
200
application/x-javascript
Script
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-71912555-1&cid=1287990128.1673973481&jid=1313694460&gjid=1575959231&_gid=1928870082.1673973481&_u=IEBAAEAAAAAAACAAI~&z=2030082772
h2
10399.189000018
10402.975999983
686
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j98&tid=UA-71912555-1&cid=1287990128.1673973481&jid=1313694460&_u=IEBAAEAAAAAAACAAI~&z=441491325
h2
10407.498000015
10417.330000026
673
42
200
image/gif
Image
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
h2
10472.794000001
10498.033999989
111295
385709
200
application/x-javascript
Script
https://www.facebook.com/tr/?id=1060466017367151&ev=PageView&dl=https%3A%2F%2Fwww.ida2at.com%2F&rl=&if=false&ts=1673973481010&sw=800&sh=600&v=2.9.92&r=stable&ec=0&o=30&fbp=fb.1.1673973481007.689033641&it=1673973480931&coo=false&rqm=GET
h2
10473.433000036
10489.383000007
328
0
200
text/plain
Image
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/pica.js
h2
10502.668000001
10584.742999985
9278
21141
200
application/javascript
Other
https://www.facebook.com/tr/?id=217037922817217&ev=PageView&dl=https%3A%2F%2Fwww.ida2at.com%2F&rl=&if=false&ts=1673973481079&sw=800&sh=600&v=2.9.92&r=stable&ec=0&o=30&cs_est=true&fbp=fb.1.1673973481007.689033641&it=1673973480931&coo=false&rqm=GET
h2
10540.336999984
10554.235999996
328
0
200
text/plain
Image
https://www.ida2at.com/cdn-cgi/rum?
h2
10948.886000027
11000.731000036
339
0
204
text/plain
XHR
https://www.facebook.com/tr/
10976.085000031
11722.233000037
0
0
-1
Ping
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/cv/result/78b0849088bc2064
h2
11717.554000032
11812.028000015
926
2
200
text/plain
XHR
https://www.facebook.com/tr/
11726.873000036
11731.878000021
0
0
-1
Ping
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)
353.121
12.57
10254.233
5.744
10259.987
6.516
10269.72
53.743
10325.025
13.79
10339.479
24.421
10369.592
6.459
10376.543
17.601
10445.326
29.111
10490.543
8.533
10528.381
12.678
10901.017
20.797
10934.531
9.675
10972.665
5.461
10981.513
737.63
12024.134
5.42
12041.017
5.719
12074.412
5.266
12107.463
5.014
12174.356
5.358
12207.496
5.047
12724.05
5.533
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

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ida2at.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Ida2at.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ida2at.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ida2at.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ida2at.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 12 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ida2at.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)
https://www.ida2at.com/wp-includes/css/dist/block-library/style-rtl.min.css?ver=6.0.1
12565
12554
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 160 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)
https://www.ida2at.com/
155.091
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ida2at.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 22 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)
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
11255
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
11254
https://connect.facebook.net/en_US/fbevents.js
45
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 429 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
111295
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
111245
https://connect.facebook.net/ar_AR/sdk.js?hash=6342d0ef33034ba9dc9facaa903b525c
89632
https://connect.facebook.net/en_US/fbevents.js
29085
https://www.ida2at.com/
23223
https://www.google-analytics.com/analytics.js
20664
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
17201
https://www.ida2at.com/wp-includes/css/dist/block-library/style-rtl.min.css?ver=6.0.1
12565
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/pica.js
9278
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
6530
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ida2at.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.8 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)
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
754.914
735.631
2.114
https://www.ida2at.com/
744.143
14.6
3.628
Minimizes main-thread work — 1.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)
Script Evaluation
862.226
Rendering
457.655
Other
207.293
Style & Layout
96.448
Script Parsing & Compilation
28.872
Parse HTML & CSS
18.264
Garbage Collection
14.534
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 27 requests • 429 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
27
438831
Script
12
388308
Document
1
23223
Other
9
13406
Stylesheet
2
12565
Image
3
1329
Media
0
0
Font
0
0
Third-party
14
373737
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)
344569
0
21279
0
6530
0
686
0
673
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)
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
893
369
Avoid non-composited animations — 2 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
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 ida2at.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

Total Blocking Time — 320 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

Reduce unused JavaScript — Potential savings of 254 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
111295
105139
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
111245
90015
https://connect.facebook.net/ar_AR/sdk.js?hash=6342d0ef33034ba9dc9facaa903b525c
89632
64798
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Ida2at.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ida2at.com/
190
https://ida2at.com/
150
https://www.ida2at.com/
0
Avoid an excessive DOM size — 1,020 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
1020
Maximum DOM Depth
20
Maximum Child Elements
22

Metrics

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

Audits

Max Potential First Input Delay — 370 ms
Users could experience a delay when interacting with the page.

Other

Serve static assets with an efficient cache policy — 8 resources found
Ida2at.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)
https://www.facebook.com/tr/?id=1060466017367151&ev=PageView&dl=https%3A%2F%2Fwww.ida2at.com%2F&rl=&if=false&ts=1673973481010&sw=800&sh=600&v=2.9.92&r=stable&ec=0&o=30&fbp=fb.1.1673973481007.689033641&it=1673973480931&coo=false&rqm=GET
0
328
https://www.facebook.com/tr/?id=217037922817217&ev=PageView&dl=https%3A%2F%2Fwww.ida2at.com%2F&rl=&if=false&ts=1673973481079&sw=800&sh=600&v=2.9.92&r=stable&ec=0&o=30&cs_est=true&fbp=fb.1.1673973481007.689033641&it=1673973480931&coo=false&rqm=GET
0
328
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
1200000
111295
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
1200000
111245
https://connect.facebook.net/en_US/fbevents.js
1200000
29085
https://www.google-analytics.com/analytics.js
7200000
20664
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
14400000
17201
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
86400000
6530
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ida2at.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.
`<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"]`
Ida2at.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
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.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ida2at.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.
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.
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
WordPress
core-js
core-js-pure@3.0.0
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 — 1 insecure request 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://ida2at.com/
Allowed

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
`window.webkitStorageInfo` is deprecated. Please use `navigator.webkitTemporaryStorage` or `navigator.webkitPersistentStorage` instead.
...
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ida2at.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 ida2at.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.
Document has 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.
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.

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 ida2at.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 ida2at.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) 69
Performance 62
Accessibility 78
Best Practices 75
SEO 88
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.ida2at.com/
Updated: 17th January, 2023

1.92 seconds
First Contentful Paint (FCP)
74%
13%
13%

0.02 seconds
First Input Delay (FID)
94%
3%
3%

Simulate loading on mobile
62

Performance

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

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ida2at.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Ida2at.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ida2at.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ida2at.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ida2at.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ida2at.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 170 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)
https://www.ida2at.com/
174.354
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ida2at.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 22 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)
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
11253
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
11252
https://connect.facebook.net/en_US/fbevents.js
45
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 414 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
111271
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
111221
https://connect.facebook.net/ar_AR/sdk.js?hash=f2b14773e514ed51750a7e9c6e38e3af
89632
https://connect.facebook.net/en_US/fbevents.js
29042
https://www.ida2at.com/
23681
https://www.google-analytics.com/analytics.js
20664
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
15203
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/pica.js
8283
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
6530
https://connect.facebook.net/ar_AR/sdk.js?ver=6.0.1
2656
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ida2at.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 — 1.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)
https://www.ida2at.com/
1705.2
45.896
11.724
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
762.076
716.196
5.644
Unattributable
130.868
5.14
0
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
111.516
86.012
23.836
https://connect.facebook.net/ar_AR/sdk.js?hash=f2b14773e514ed51750a7e9c6e38e3af
88.44
71.016
16.76
https://www.google-analytics.com/analytics.js
75.048
64.024
2.968
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
54.476
31.136
21.352
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 27 requests • 414 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
27
423643
Script
12
386219
Document
1
23681
Other
9
12414
Image
3
1329
Stylesheet
2
0
Media
0
0
Font
0
0
Third-party
14
373646
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)
344478
17.264
21279
6.06
6530
0
686
0
673
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 — 5 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)
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
3161
366
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
5474
94
https://www.ida2at.com/
2089
78
https://www.google-analytics.com/analytics.js
3810
61
https://connect.facebook.net/ar_AR/sdk.js?hash=f2b14773e514ed51750a7e9c6e38e3af
4080
56
Avoid non-composited animations — 2 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
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 ida2at.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://ida2at.com/
http/1.1
0
88.900999980979
773
0
301
text/plain
https://ida2at.com/
http/1.1
89.217999950051
196.29799999529
795
0
301
text/plain
https://www.ida2at.com/
h2
196.66299998062
370.02199998824
23681
152186
200
text/html
Document
https://www.ida2at.com/wp-includes/css/dist/block-library/style-rtl.min.css?ver=6.0.1
379.25800000085
10272.065999976
0
0
-1
Stylesheet
https://www.ida2at.com/wp-content/themes/ida2at/assets/styles/main.css?ver=1673797040
379.56499995198
10271.01299999
0
0
-1
Stylesheet
https://www.ida2at.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
379.72799997078
10273.553999956
0
0
-1
Script
https://www.ida2at.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2
379.89300000481
10272.995000007
0
0
-1
Script
https://connect.facebook.net/ar_AR/sdk.js?ver=6.0.1
h2
381.05099997483
405.07699997397
2656
3093
200
application/x-javascript
Script
https://www.ida2at.com/wp-content/themes/ida2at/assets/scripts/vendor.min.js
380.2479999722
10273.184999998
0
0
-1
Script
https://www.ida2at.com/wp-content/themes/ida2at/assets/scripts/main.js
380.43899997137
10282.804999966
0
0
-1
Script
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
h2
10273.876999971
10334.85699998
6530
17031
200
text/javascript
Script
https://connect.facebook.net/ar_AR/sdk.js?hash=f2b14773e514ed51750a7e9c6e38e3af
h2
10277.472999995
10307.070999988
89632
314360
200
application/x-javascript
Script
https://www.google-analytics.com/analytics.js
h2
10277.654999983
10284.301000007
20664
50230
200
text/javascript
Script
https://connect.facebook.net/en_US/fbevents.js
h2
10277.775999974
10304.001999961
29042
108596
200
application/x-javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=1695841726&t=pageview&_s=1&dl=https%3A%2F%2Fwww.ida2at.com%2F&ul=en-us&de=UTF-8&dt=%D8%A5%D8%B6%D8%A7%D8%A1%D8%A7%D8%AA%20%E2%80%93%20%D9%85%D8%AD%D8%AA%D9%88%D9%89%20%D8%B9%D8%B1%D8%A8%D9%8A%20%D8%AB%D8%B1%D9%8A&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAACAAI~&jid=1276811329&gjid=901066297&cid=923104307.1673973532&tid=UA-71912555-1&_gid=221875693.1673973532&_r=1&_slc=1&z=1351402345
h2
10352.810999961
10363.016999967
615
4
200
text/plain
XHR
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
h2
10367.455
10450.378999987
111221
385574
200
application/x-javascript
Script
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
h2
10371.366999985
10405.978999974
15203
35217
200
application/javascript
Script
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-71912555-1&cid=923104307.1673973532&jid=1276811329&gjid=901066297&_gid=221875693.1673973532&_u=IEBAAEAAAAAAACAAI~&z=1319901037
h2
10390.014999954
10400.78799997
686
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j98&tid=UA-71912555-1&cid=923104307.1673973532&jid=1276811329&_u=IEBAAEAAAAAAACAAI~&z=766056109
h2
10403.027999972
10419.729999965
673
42
200
image/gif
Image
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/pica.js
h2
10421.648999967
10476.500999997
8283
18663
200
application/javascript
Other
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
h2
10489.809999999
10564.722999989
111271
385709
200
application/x-javascript
Script
https://www.facebook.com/tr/?id=1060466017367151&ev=PageView&dl=https%3A%2F%2Fwww.ida2at.com%2F&rl=&if=false&ts=1673973531710&sw=360&sh=640&v=2.9.92&r=stable&ec=0&o=30&fbp=fb.1.1673973531708.549923222&it=1673973531588&coo=false&rqm=GET
h2
10490.065999969
10517.281999986
328
0
200
text/plain
Image
https://www.facebook.com/tr/?id=217037922817217&ev=PageView&dl=https%3A%2F%2Fwww.ida2at.com%2F&rl=&if=false&ts=1673973531813&sw=360&sh=640&v=2.9.92&r=stable&ec=0&o=30&cs_est=true&fbp=fb.1.1673973531708.549923222&it=1673973531588&coo=false&rqm=GET
h2
10592.566000007
10621.652000002
328
0
200
text/plain
Image
https://www.ida2at.com/cdn-cgi/rum?
h2
10635.588000005
10675.797000004
339
0
204
text/plain
XHR
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/cv/result/78b085cd3a8d0331
h2
10935.100999952
11050.826999999
923
2
200
text/plain
XHR
https://www.facebook.com/tr/
10992.446999997
10995.760999969
0
0
-1
Ping
https://www.facebook.com/tr/
11095.973999996
11097.856999957
0
0
-1
Ping
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)
374.05
10.31
10285.797
39.219
10325.568
8.719
10338.842
15.369
10357.574
11.047
10372.679
14.108
10467.714
23.438
10583.142
10.271
10624.547
8.866
10753.229
183.237
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

First Contentful Paint — 2.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 5.4 s
The time taken for the page to become fully interactive.
Total Blocking Time — 360 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).
Largest Contentful Paint — 3.9 s
The timing of the largest text or image that is painted.

Audits

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

Other

Avoid an excessive DOM size — 1,020 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
1020
Maximum DOM Depth
20
Maximum Child Elements
22
Minimize main-thread work — 3.0 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
1085.74
Rendering
852.08
Other
577.36
Style & Layout
333.536
Script Parsing & Compilation
90.304
Parse HTML & CSS
41.372
Garbage Collection
34.408

Metrics

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

Audits

Max Potential First Input Delay — 370 ms
Users could experience a delay when interacting with the page.

Other

Reduce unused JavaScript — Potential savings of 254 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
111271
105116
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
111221
89996
https://connect.facebook.net/ar_AR/sdk.js?hash=f2b14773e514ed51750a7e9c6e38e3af
89632
64828
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Ida2at.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ida2at.com/
630
https://ida2at.com/
480
https://www.ida2at.com/
0
Serve static assets with an efficient cache policy — 8 resources found
Ida2at.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)
https://www.facebook.com/tr/?id=1060466017367151&ev=PageView&dl=https%3A%2F%2Fwww.ida2at.com%2F&rl=&if=false&ts=1673973531710&sw=360&sh=640&v=2.9.92&r=stable&ec=0&o=30&fbp=fb.1.1673973531708.549923222&it=1673973531588&coo=false&rqm=GET
0
328
https://www.facebook.com/tr/?id=217037922817217&ev=PageView&dl=https%3A%2F%2Fwww.ida2at.com%2F&rl=&if=false&ts=1673973531813&sw=360&sh=640&v=2.9.92&r=stable&ec=0&o=30&cs_est=true&fbp=fb.1.1673973531708.549923222&it=1673973531588&coo=false&rqm=GET
0
328
https://connect.facebook.net/signals/config/217037922817217?v=2.9.92&r=stable
1200000
111271
https://connect.facebook.net/signals/config/1060466017367151?v=2.9.92&r=stable
1200000
111221
https://connect.facebook.net/en_US/fbevents.js
1200000
29042
https://www.google-analytics.com/analytics.js
7200000
20664
https://www.ida2at.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1673971200
14400000
15203
https://static.cloudflareinsights.com/beacon.min.js/vaafb692b2aea4879b33c060e79fe94621666317369993
86400000
6530
First Contentful Paint (3G) — 5580 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ida2at.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.
`<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"]`
Ida2at.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
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.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ida2at.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.
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.
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
WordPress
core-js
core-js-pure@3.0.0
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 — 1 insecure request 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://ida2at.com/
Allowed

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
`window.webkitStorageInfo` is deprecated. Please use `navigator.webkitTemporaryStorage` or `navigator.webkitPersistentStorage` instead.
...
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
88

SEO

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

Mobile Friendly

Tap targets are not sized appropriately — 66% 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
13x13
21x17
21x17
30x17
30x17
30x17
34x17
30x17
39x17
39x17
40x17
39x17
88x17
105x17
52x17
68x17
63x17
69x17
94x17
24x24
24x24
24x24
24x24
32x32
39x17
24x24
24x24
24x24
40x17
158x21
49x17
24x24
24x24
24x24
24x24
24x24
24x24
24x24
24x24

Crawling and Indexing

robots.txt is not valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

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

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 ida2at.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 ida2at.com 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.
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: 104.26.7.140
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
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

Name IP Address
Cloudflare, Inc. 104.16.123.96
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: ida2at.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 10th May, 2022
Valid To: 10th May, 2023
Subject: CN = ida2at.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: a0bbd0f0
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 12171526010800706169071867756119593511
Serial Number (Hex): 092826906DC73CCAB9E2B05710941227
Valid From: 10th May, 2024
Valid To: 10th May, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : May 10 02:18:41.040 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:51:4B:22:0C:1C:15:86:73:7C:A2:E9:82:
79:CF:AA:7C:0A:A5:FE:A0:D2:BC:F5:98:13:A9:27:87:
09:96:7C:A6:02:21:00:E4:42:E2:7F:B7:5C:0F:06:0F:
81:D9:44:00:02:D5:C5:48:95:1C:78:0C:92:CB:12:DC:
A7:1E:B5:1D:28:1C:B7
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : May 10 02:18:41.099 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:C7:25:7E:0C:C0:C5:2C:58:6A:30:4F:
FA:5C:78:F5:A9:26:28:F2:3C:63:0D:84:DA:2C:A0:32:
63:6C:7B:B2:16:02:20:2F:C8:73:94:15:0F:21:C3:D9:
9D:AD:9E:83:AB:70:04:FF:2C:53:52:90:2A:11:58:D5:
F0:B9:AD:A7:E1:98:A9
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : May 10 02:18:41.094 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:13:07:B6:A8:62:93:48:D7:52:E9:53:FD:
FB:F8:FF:5E:BC:CD:59:3B:6C:AE:BC:E4:6A:4B:F7:95:
4D:36:93:35:02:21:00:B5:36:BD:BD:FB:DF:39:33:D7:
15:CD:2A:81:48:B6:F8:F5:B7:20:93:3A:25:03:D2:19:
D6:FE:8C:EE:57:C4:46
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.ida2at.com
DNS:ida2at.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 17th January, 2023
Content-Type: text/html; charset=UTF-8
Cache-Control: max-age=1800
Expires: 15th January, 2023
Server: cloudflare
Connection: keep-alive
CF-Ray: 78b082f84dd40cd9-EWR
Age: 63319
Last-Modified: 15th August, 2022
Vary: X-Forwarded-Proto,Accept-Encoding
CF-Cache-Status: HIT
cf-apo-via: tcache
Server-Timing: cf-q-config;dur=6.0000002122251e-06
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=Bs2ZvvUHkyag1xWsVzVuZ%2FBwhYA6heOz4ynNHepYkCVxJiKaHs718ZtLk3nq3Ye%2FH8pOC4rzAeOLkqGzxRrSsaTpAuiEkS%2Bl3lmXKtq1WXY4lV9wEEejwl1l4819wGXd"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 8th February, 2015
Changed: 15th January, 2023
Expires: 8th February, 2024
Registrar: Cloudflare, Inc.
Status:
Nameservers: april.ns.cloudflare.com
merlin.ns.cloudflare.com
Owner Name: DATA REDACTED
Owner Organization: DATA REDACTED
Owner Street: DATA REDACTED
Owner Post Code: DATA REDACTED
Owner City: DATA REDACTED
Owner State: Giza
Owner Country: EG
Owner Phone: DATA REDACTED
Owner Email: https://domaincontact.cloudflareregistrar.com/ida2at.com
Admin Name: DATA REDACTED
Admin Organization: DATA REDACTED
Admin Street: DATA REDACTED
Admin Post Code: DATA REDACTED
Admin City: DATA REDACTED
Admin State: DATA REDACTED
Admin Country: DATA REDACTED
Admin Phone: DATA REDACTED
Admin Email: https://domaincontact.cloudflareregistrar.com/ida2at.com
Tech Name: DATA REDACTED
Tech Organization: DATA REDACTED
Tech Street: DATA REDACTED
Tech Post Code: DATA REDACTED
Tech City: DATA REDACTED
Tech State: DATA REDACTED
Tech Country: DATA REDACTED
Tech Phone: DATA REDACTED
Tech Email: https://domaincontact.cloudflareregistrar.com/ida2at.com
Billing Name: DATA REDACTED
Billing Organization: DATA REDACTED
Billing Street: DATA REDACTED
Billing Post Code: DATA REDACTED
Billing City: DATA REDACTED
Billing State: DATA REDACTED
Billing Country: DATA REDACTED
Billing Phone: DATA REDACTED
Billing Fax: DATA REDACTED
Billing Email: https://domaincontact.cloudflareregistrar.com/ida2at.com
Full Whois: Domain Name: IDA2AT.COM
Registry Domain ID: 1901467069_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: https://www.cloudflare.com
Updated Date: 2023-01-15T09:12:28Z
Creation Date: 2015-02-08T12:22:04Z
Registrar Registration Expiration Date: 2024-02-08T12:22:04Z
Registrar: Cloudflare, Inc.
Registrar IANA ID: 1910
Domain Status: clienttransferprohibited https://icann.org/epp#clienttransferprohibited
Registry Registrant ID:
Registrant Name: DATA REDACTED
Registrant Organization: DATA REDACTED
Registrant Street: DATA REDACTED
Registrant City: DATA REDACTED
Registrant State/Province: Giza
Registrant Postal Code: DATA REDACTED
Registrant Country: EG
Registrant Phone: DATA REDACTED
Registrant Phone Ext: DATA REDACTED
Registrant Fax: DATA REDACTED
Registrant Fax Ext: DATA REDACTED
Registrant Email: https://domaincontact.cloudflareregistrar.com/ida2at.com
Registry Admin ID:
Admin Name: DATA REDACTED
Admin Organization: DATA REDACTED
Admin Street: DATA REDACTED
Admin City: DATA REDACTED
Admin State/Province: DATA REDACTED
Admin Postal Code: DATA REDACTED
Admin Country: DATA REDACTED
Admin Phone: DATA REDACTED
Admin Phone Ext: DATA REDACTED
Admin Fax: DATA REDACTED
Admin Fax Ext: DATA REDACTED
Admin Email: https://domaincontact.cloudflareregistrar.com/ida2at.com
Registry Tech ID:
Tech Name: DATA REDACTED
Tech Organization: DATA REDACTED
Tech Street: DATA REDACTED
Tech City: DATA REDACTED
Tech State/Province: DATA REDACTED
Tech Postal Code: DATA REDACTED
Tech Country: DATA REDACTED
Tech Phone: DATA REDACTED
Tech Phone Ext: DATA REDACTED
Tech Fax: DATA REDACTED
Tech Fax Ext: DATA REDACTED
Tech Email: https://domaincontact.cloudflareregistrar.com/ida2at.com
Registry Billing ID:
Billing Name: DATA REDACTED
Billing Organization: DATA REDACTED
Billing Street: DATA REDACTED
Billing City: DATA REDACTED
Billing State/Province: DATA REDACTED
Billing Postal Code: DATA REDACTED
Billing Country: DATA REDACTED
Billing Phone: DATA REDACTED
Billing Phone Ext: DATA REDACTED
Billing Fax: DATA REDACTED
Billing Fax Ext: DATA REDACTED
Billing Email: https://domaincontact.cloudflareregistrar.com/ida2at.com
Name Server: april.ns.cloudflare.com
Name Server: merlin.ns.cloudflare.com
DNSSEC: unsigned
Registrar Abuse Contact Email: registrar-abuse@cloudflare.com
Registrar Abuse Contact Phone: +1.4153197517
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-01-17T16:36:47Z <<<

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

Cloudflare provides more than 13 million domains with the tools to give their global users a faster, more secure, and more reliable internet experience.

NOTICE:

Data in the Cloudflare Registrar WHOIS database is provided to you by Cloudflare
under the terms and conditions at https://www.cloudflare.com/domain-registration-agreement/

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

Register your domain name at https://www.cloudflare.com/registrar/

Nameservers

Name IP Address
april.ns.cloudflare.com 172.64.32.66
merlin.ns.cloudflare.com 173.245.59.205
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address