Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

zydusconnect.com

zydusconnect.com may not be SSL secured

Free website and domain report on zydusconnect.com

Last Updated: 31st December, 2021 Update Now
Overview

Snoop Summary for zydusconnect.com

This is a free and comprehensive report about zydusconnect.com. The domain zydusconnect.com is currently hosted on a server located in India with the IP address 203.88.147.131, where the local currency is INR and English is the local language. Our records indicate that zydusconnect.com is owned/operated by Cadila Healthcare Limited. If zydusconnect.com was to be sold it would possibly be worth $651 USD (based on the daily revenue potential of the website over a 24 month period). Zydusconnect.com receives an estimated 308 unique visitors every day - a decent amount of traffic! This report was last updated 31st December, 2021.

About zydusconnect.com

Site Preview: zydusconnect.com zydusconnect.com
Title: SAP NetWeaver Portal
Description:
Keywords and Tags: business
Related Terms:
Fav Icon:
Age: Over 14 years old
Domain Created: 3rd March, 2010
Domain Updated: 1st March, 2021
Domain Expires: 3rd March, 2022
Review

Snoop Score

1/5

Valuation

$651 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 4,505,410
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: 308
Monthly Visitors: 9,375
Yearly Visitors: 112,420
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $27 USD
Yearly Revenue: $320 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: zydusconnect.com 16
Domain Name: zydusconnect 12
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 62
Performance 95
Accessibility 78
Best Practices 69
SEO 70
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
95

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
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).
Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.015
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 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://zydusconnect.com/
http/1.1
0
623.06699994951
255
0
307
text/html
http://zydusconnect.com/irj/portal
http/1.1
623.41300025582
1285.9779996797
3747
8833
200
text/html
Document
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
http/1.1
1297.7809999138
2250.3880001605
5386
5178
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
http/1.1
1298.0479998514
1930.2260000259
633
426
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
http/1.1
1298.3740000054
2804.8149999231
58003
57778
200
application/x-javascript
Script
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
http/1.1
1298.746000044
2523.9230003208
26000
230890
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/logon.css
http/1.1
1299.080000259
1920.2129999176
324
117
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/main2.css
http/1.1
1299.290000461
1587.507000193
2852
17826
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/js/basic.js
http/1.1
1299.6140001342
1921.4930003509
962
739
200
application/x-javascript
Script
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
http/1.1
2525.8219996467
3386.2389996648
15810
15600
200
image/gif
Image
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
http/1.1
2809.6190001816
3668.5779998079
15454
15243
200
image/jpeg
Image
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/common/label/3x1_label_designbar.gif?7.0.16.1.0
http/1.1
2827.5239998475
3113.9639997855
250
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1328.434
7.891
2849.473
23.525
2873.011
7.879
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 — Potential savings of 15 KiB
Images can slow down the page's load time. Zydusconnect.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
15600
15556
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Zydusconnect.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Zydusconnect.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Zydusconnect.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 25 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Zydusconnect.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://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
26000
25874
Reduce unused JavaScript — Potential savings of 45 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://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
58003
46126
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 — Potential savings of 47 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
57778
44197
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
5178
4200
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Zydusconnect.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://zydusconnect.com/
190
http://zydusconnect.com/irj/portal
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Zydusconnect.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
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.
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 127 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
58003
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
26000
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
15810
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
15454
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
5386
http://zydusconnect.com/irj/portal
3747
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/main2.css
2852
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/js/basic.js
962
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
633
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/logon.css
324
Avoids an excessive DOM size — 77 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
77
Maximum DOM Depth
 *
17
Maximum Child Elements
To unlock or reset password, please login through ZydusPortal. : 1) Intranet …
13
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Zydusconnect.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
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.
Minimizes main-thread work — 0.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)
Other
27.985
Style & Layout
15.252
Script Evaluation
13.68
Parse HTML & CSS
8.677
Rendering
7.231
Script Parsing & Compilation
3.184
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 — 12 requests • 127 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
12
129676
Script
2
58965
Stylesheet
5
35195
Image
3
31514
Document
1
3747
Other
1
255
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
Zydus Cadila Ltd.
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.
Element
Zydus Cadila Ltd.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Welcome to Zydus Connect User ID (Emp ID)  * Password  *   To unl…
0.014639412923562
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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

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

Other

Eliminate render-blocking resources — Potential savings of 270 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Zydusconnect.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://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
5386
70
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
633
110
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
58003
270
Serve static assets with an efficient cache policy — 10 resources found
Zydusconnect.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://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
86400000
58003
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
86400000
26000
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
86400000
15810
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
86400000
15454
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
86400000
5386
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/main2.css
86400000
2852
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/js/basic.js
86400000
962
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
86400000
633
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/logon.css
86400000
324
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/common/label/3x1_label_designbar.gif?7.0.16.1.0
86400000
250

Other

Reduce initial server response time — Root document took 660 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://zydusconnect.com/irj/portal
663.559
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of zydusconnect.com on mobile screens.
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of zydusconnect.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.
`<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 `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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

Internationalization and localization

`<html>` element does not have 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.
Failing Elements
html

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
td > form#umLogonPage > span.urTxtStd > img

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that zydusconnect.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

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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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 — 12 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://zydusconnect.com/
Allowed
http://zydusconnect.com/irj/portal
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/logon.css
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/main2.css
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/js/basic.js
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/common/label/3x1_label_designbar.gif?7.0.16.1.0
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Registers an `unload` listener
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.
Source
SHOW DETAILS
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
SHOW DETAILS
DOMException: Failed to set the 'domain' property on 'Document': 'com' is a top-level domain. at Object.EPCM.relaxDocumentDomain (http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600:125:16) at http://zydusconnect.com/irj/portal:9:6
70

SEO

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

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

Mobile Friendly

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of zydusconnect.com on mobile screens.

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.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
td > form#umLogonPage > span.urTxtStd > img

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

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

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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of zydusconnect.com on mobile screens.
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) 58
Performance 93
Accessibility 78
Best Practices 62
SEO 58
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
93

Performance

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

Metrics

Time to Interactive — 2.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 30 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 — 2.5 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.008
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.
First Meaningful Paint — 2.2 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://zydusconnect.com/
http/1.1
0
363.71399997734
228
0
307
text/html
http://zydusconnect.com/irj/portal
http/1.1
364.09899999853
662.62099996675
3747
8833
200
text/html
Document
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
http/1.1
675.87599996477
1250.2300000051
5386
5178
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
http/1.1
676.34300002828
970.62699997332
633
426
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
http/1.1
676.74799996894
1862.579000066
58003
57778
200
application/x-javascript
Script
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
http/1.1
677.68299998716
1533.8270000648
26000
230890
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/logon.css
http/1.1
677.9010000173
1247.1059999662
324
117
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/main2.css
http/1.1
678.26900002547
1247.7450000588
2852
17826
200
text/css
Stylesheet
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/js/basic.js
http/1.1
678.53500007186
966.66799997911
962
739
200
application/x-javascript
Script
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
http/1.1
1535.6260000262
2390.3260000516
15810
15600
200
image/gif
Image
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
http/1.1
1866.0920000402
2715.8340000315
15454
15243
200
image/jpeg
Image
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/common/label/3x1_label_designbar.gif?7.0.16.1.0
http/1.1
1887.7370000118
2171.9189999858
250
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
710.649
8.396
1910.877
25.392
1936.284
9.271
2768.394
18.891
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 — Potential savings of 15 KiB
Images can slow down the page's load time. Zydusconnect.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
15600
15294
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Zydusconnect.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Zydusconnect.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Zydusconnect.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 25 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Zydusconnect.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://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
26000
25874
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.
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 300 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://zydusconnect.com/irj/portal
299.516
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Zydusconnect.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://zydusconnect.com/
630
http://zydusconnect.com/irj/portal
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Zydusconnect.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
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.
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 127 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
58003
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
26000
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
15810
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
15454
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
5386
http://zydusconnect.com/irj/portal
3747
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/main2.css
2852
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/js/basic.js
962
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
633
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/logon.css
324
Avoids an excessive DOM size — 77 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
77
Maximum DOM Depth
 *
17
Maximum Child Elements
To unlock or reset password, please login through ZydusPortal. : 1) Intranet …
13
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Zydusconnect.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://zydusconnect.com/irj/portal
275.348
31.028
7.784
Unattributable
82.736
11.968
0.724
Minimizes main-thread work — 0.4 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)
Other
111.368
Rendering
105.452
Style & Layout
62.136
Script Evaluation
58.608
Parse HTML & CSS
38.936
Script Parsing & Compilation
13.184
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 — 12 requests • 127 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
12
129649
Script
2
58965
Stylesheet
5
35195
Image
3
31514
Document
1
3747
Other
1
228
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
Zydus Cadila Ltd.
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.
Element
Zydus Cadila Ltd.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Welcome to Zydus Connect User ID (Emp ID)  * Password  *   To unl…
0.0084016152726803
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://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
2370
102
http://zydusconnect.com/irj/portal
652
76
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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 — 2.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 4.2 s
The time taken for the page contents to be visibly populated.

Other

Eliminate render-blocking resources — Potential savings of 790 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Zydusconnect.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://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
5386
330
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
633
330
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
58003
1080
Reduce unused JavaScript — Potential savings of 45 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://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
58003
46126
Enable text compression — Potential savings of 47 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
57778
44197
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
5178
4200
Serve static assets with an efficient cache policy — 10 resources found
Zydusconnect.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://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
86400000
58003
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
86400000
26000
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
86400000
15810
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
86400000
15454
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
86400000
5386
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/main2.css
86400000
2852
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/js/basic.js
86400000
962
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
86400000
633
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/logon.css
86400000
324
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/common/label/3x1_label_designbar.gif?7.0.16.1.0
86400000
250
First Contentful Paint (3G) — 4332 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of zydusconnect.com on mobile screens.
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of zydusconnect.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.
`<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 `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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

Internationalization and localization

`<html>` element does not have 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.
Failing Elements
html

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
td > form#umLogonPage > span.urTxtStd > img

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that zydusconnect.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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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 — 12 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://zydusconnect.com/
Allowed
http://zydusconnect.com/irj/portal
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/glbl/glbl_nn7.css?7.0.16.0.0
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/sap_tradeshow/prtl_std/prtl_std_nn7.css?7.0.16.0.0
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/ur/ur_nn7.css?7.0.16.0.0
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/logon.css
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/css/main2.css
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/js/basic.js
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/unlock1.gif
Allowed
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
Allowed
http://zydusconnect.com/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/sap_tradeshow/common/label/3x1_label_designbar.gif?7.0.16.1.0
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
http://zydusconnect.com/irj/portalapps/ZydusLogonPage/layout/Zydus_Portal1.jpg
361 x 337
361 x 337
722 x 674

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Registers an `unload` listener
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.
Source
SHOW DETAILS
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
SHOW DETAILS
DOMException: Failed to set the 'domain' property on 'Document': 'com' is a top-level domain. at Object.EPCM.relaxDocumentDomain (http://zydusconnect.com/irj/portalapps/com.sap.portal.epcf.loader/script/optimize/js13_epcf.js?7.00001600:125:16) at http://zydusconnect.com/irj/portal:9:6
58

SEO

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

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

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of zydusconnect.com on mobile screens.
Document doesn't use 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 not 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 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.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
td > form#umLogonPage > span.urTxtStd > img

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

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 zydusconnect.com. This includes details about web app manifests.

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
Content is not 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of zydusconnect.com on mobile screens.
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: 203.88.147.131
Continent: Asia
Country: India
India Flag
Region:
City:
Longitude: 77
Latitude: 20
Currencies: INR
Languages: English
Hindi
Tamil

Web Hosting Provider

Name IP Address
YOU Telecom India Pvt Ltd
Registration

Domain Registrant

Private Registration: No
Name: Jayesh Bhavsar
Organization: Cadila Healthcare Limited
Country: IN
City: Ahmedabad
State: Gujarat
Post Code: 380015
Email: daemonindia@gmail.com
Phone: +91.7926868100
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
PDR Ltd. d/b/a PublicDomainRegistry.com 104.16.180.120
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

Technical

DNS Lookup

A Records

Host IP Address Class TTL
zydusconnect.com. 203.88.147.131 IN 14400

NS Records

Host Nameserver Class TTL
zydusconnect.com. ns2.xoomdns.in. IN 21600
zydusconnect.com. ns1.xoomdns.in. IN 21600

MX Records

Priority Host Server Class TTL
0 zydusconnect.com. zydusconnect.com. IN 14400

SOA Records

Domain Name Primary NS Responsible Email TTL
zydusconnect.com. ns1.xoomdns.in. server.rikin.in. 21600

TXT Records

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

HTTP Response Headers

HTTP-Code: HTTP/1.0 307 Temporary Redirect
date: 31st December, 2021
content-type: text/html
server: SAP NetWeaver Application Server (ICM)
connection: close
location: /irj/portal

Whois Lookup

Created: 3rd March, 2010
Changed: 1st March, 2021
Expires: 3rd March, 2022
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Status: clientTransferProhibited
Nameservers: ns1.daemonhost.com
ns2.daemonhost.com
Owner Name: Amit Arora
Owner Organization: Cadila Healthcare Limited
Owner Street: Zydus Tower, Satellite
Owner Post Code: 380015
Owner City: Ahmedabad
Owner State: Gujarat
Owner Country: IN
Owner Phone: +91.8200605224
Owner Email: licensing@zyduscadila.com
Admin Name: Amit Arora
Admin Organization: Cadila Healthcare Limited
Admin Street: Zydus Tower, Satellite
Admin Post Code: 380015
Admin City: Ahmedabad
Admin State: Gujarat
Admin Country: IN
Admin Phone: +91.8200605224
Admin Email: licensing@zyduscadila.com
Tech Name: Amit Arora
Tech Organization: Cadila Healthcare Limited
Tech Street: Zydus Tower, Satellite
Tech Post Code: 380015
Tech City: Ahmedabad
Tech State: Gujarat
Tech Country: IN
Tech Phone: +91.8200605224
Tech Email: licensing@zyduscadila.com
Full Whois: Domain Name: ZYDUSCONNECT.COM
Registry Domain ID: 1587352629_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.publicdomainregistry.com
Registrar URL: www.publicdomainregistry.com
Updated Date: 2021-03-01T06:05:24Z
Creation Date: 2010-03-03T13:20:09Z
Registrar Registration Expiration Date: 2022-03-03T13:20:09Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Amit Arora
Registrant Organization: Cadila Healthcare Limited
Registrant Street: Zydus Tower, Satellite
Registrant City: Ahmedabad
Registrant State/Province: Gujarat
Registrant Postal Code: 380015
Registrant Country: IN
Registrant Phone: +91.8200605224
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: licensing@zyduscadila.com
Registry Admin ID: Not Available From Registry
Admin Name: Amit Arora
Admin Organization: Cadila Healthcare Limited
Admin Street: Zydus Tower, Satellite
Admin City: Ahmedabad
Admin State/Province: Gujarat
Admin Postal Code: 380015
Admin Country: IN
Admin Phone: +91.8200605224
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: licensing@zyduscadila.com
Registry Tech ID: Not Available From Registry
Tech Name: Amit Arora
Tech Organization: Cadila Healthcare Limited
Tech Street: Zydus Tower, Satellite
Tech City: Ahmedabad
Tech State/Province: Gujarat
Tech Postal Code: 380015
Tech Country: IN
Tech Phone: +91.8200605224
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: licensing@zyduscadila.com
Name Server: ns1.daemonhost.com
Name Server: ns2.daemonhost.com
DNSSEC: Unsigned
Registrar Abuse Contact Email: abuse-contact@publicdomainregistry.com
Registrar Abuse Contact Phone: +1.2013775952
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-12-31T12:59:29Z <<<

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

Registration Service Provided By: WEB4INDIA

The data in this whois database is provided to you for information purposes
only, that is, to assist you in obtaining information about or related to a
domain name registration record. We make this information available "as is",
and do 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:
(1) enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or
(2) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic mail, or
by telephone.
The compilation, repackaging, dissemination or other use of this data is
expressly prohibited without prior written consent from us. The Registrar of
record is PDR Ltd. d/b/a PublicDomainRegistry.com.
We reserve the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.
View Raw Whois

Nameservers

Name IP Address
ns1.daemonhost.com 96.125.165.31
ns2.daemonhost.com 96.125.165.42
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Love W3 Snoop?
Update Now

Recently Updated

watanserb.com
ksaexperience.com
rijalmagazine.com
leparisien.com
yasmina.com
leparisien.fr
timeoutriyadh.com
1webcam.org
menews247.com
executive-bulletin.com

Recently Viewed

agocer.com
edocourier.com
fabrictech.com
shchuanghui.com
hhmai.com
apknote.com
thecityoflights.net
veronikaratulovska.com
shfju.org
cosmeticare.com