tellmands.in

tellmands.in may not be SSL secured

Free website and domain report on tellmands.in

Last Updated: 26th October, 2021 Update Now
Overview

Snoop Summary for tellmands.in

This is a free and comprehensive report about tellmands.in. The domain tellmands.in is currently hosted on a server located in United States with the IP address 3.33.152.147, where the local currency is USD and English is the local language. If tellmands.in was to be sold it would possibly be worth $370 USD (based on the daily revenue potential of the website over a 24 month period). Tellmands.in receives an estimated 173 unique visitors every day - a decent amount of traffic! This report was last updated 26th October, 2021.

What is tellmands.in?

An online survey/customer feedback site for Marks & Spencer, a major british retailer that sells high quality clothing, food and home products.

About tellmands.in

Site Preview: tellmands.in tellmands.in
Title:
Description:
Keywords and Tags: internet services, retail, surveys
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

Valuation

$370 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,906,298
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: 173
Monthly Visitors: 5,266
Yearly Visitors: 63,145
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $15 USD
Yearly Revenue: $180 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: tellmands.in 12
Domain Name: tellmands 9
Extension (TLD): in 2

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 60
Performance 81
Accessibility 79
Best Practices 67
SEO 55
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
81

Performance

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

Metrics

Time to Interactive — 1.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 40 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.024
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Tellmands.in should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tellmands.in should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 6 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tellmands.in should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
26805
5831
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tellmands.in should consider minifying JS files.
Reduce unused CSS — Potential savings of 37 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tellmands.in should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
26805
24606
http://www.tellmands.in/websurvey/css/third-party.min.css
12995
12968
Reduce unused JavaScript — Potential savings of 126 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://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
179703
91784
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
73900
37586
Efficiently encode images — Potential savings of 17 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=5e7709b7-7f80-301d-b083-54a3dc7f0842&v=1&type=0&tag=INposEntrySpring19EN
171434
10018
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=7c7467d2-52b0-0d3f-87c7-81e3d35ec37b&v=0&type=0&tag=MNSheader
20033
6890
Serve images in next-gen formats — Potential savings of 106 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=5e7709b7-7f80-301d-b083-54a3dc7f0842&v=1&type=0&tag=INposEntrySpring19EN
171434
93947.2
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=7c7467d2-52b0-0d3f-87c7-81e3d35ec37b&v=0&type=0&tag=MNSheader
20033
14403.25
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 250 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
251.798
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tellmands.in 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 13 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
6527
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
6508
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 557 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
179703
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=5e7709b7-7f80-301d-b083-54a3dc7f0842&v=1&type=0&tag=INposEntrySpring19EN
171899
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
73900
http://www.tellmands.in/websurvey/css/webfonts/calibri-webfont.woff
38115
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
26805
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=7c7467d2-52b0-0d3f-87c7-81e3d35ec37b&v=0&type=0&tag=MNSheader
20480
http://www.tellmands.in/websurvey/css/third-party.min.css
12995
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=d77ee9f3-d173-4050-a4ad-03b723e8fd47&v=0&type=0&tag=logo
6033
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
5273
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
5247
Uses efficient cache policy on static assets — 2 resources found
Tellmands.in 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://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
999999000
26805
http://www.tellmands.in/websurvey/2/retrieveJs.js?imData=t&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
999999000
1003
Avoids an excessive DOM size — 119 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
119
Maximum DOM Depth
20
Maximum Child Elements
11
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Tellmands.in should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
933.164
692.475
9.47
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
67.194
6.735
2.652
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
705.545
Style & Layout
204.74
Other
69.968
Parse HTML & CSS
34.721
Rendering
20.906
Script Parsing & Compilation
17.511
Keep request counts low and transfer sizes small — 26 requests • 557 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
26
569915
Script
3
254606
Image
10
215838
Stylesheet
2
39800
Font
1
38115
Other
9
16283
Document
1
5273
Media
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
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
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.015582241114412
0.0080424470267932
0.00032839992026072
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://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
1140
356
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
1880
64
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 tellmands.in on mobile screens.

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.

Other

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://tellmands.in/
http/1.1
0
145.37699986249
345
0
301
text/html
http://www.tellmands.in/
http/1.1
146.11299987882
344.8840000201
210
0
302
text/plain
http://www.tellmands.in/websurvey/app
http/1.1
345.54399992339
436.48199993186
548
0
302
text/html
http://www.tellmands.in/websurvey/2/begin
http/1.1
437.33799993061
711.28899999894
537
0
303
text/plain
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
http/1.1
712.03999989666
962.84699998796
5273
14970
200
text/html
Document
http://www.tellmands.in/websurvey/css/third-party.min.css
http/1.1
978.94899989478
1071.3939999696
12995
104810
200
text/css
Stylesheet
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
http/1.1
979.11600000225
1305.4719998036
179703
542364
200
application/javascript
Script
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
http/1.1
979.42999983206
1233.6319999304
73900
304325
200
application/javascript
Script
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
http/1.1
979.83499988914
1255.4049999453
26805
186639
200
text/css
Stylesheet
http://www.tellmands.in/websurvey/2/retrieveJs.js?imData=t&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
http/1.1
980.0999998115
1156.915999949
1003
1128
200
application/javascript
Script
http://www.tellmands.in/websurvey/image/info.png
http/1.1
1259.2709998135
1343.3139999397
1521
1142
200
image/png
Image
http://www.tellmands.in/websurvey/image/remove.png
http/1.1
1342.0419998001
1575.1049998216
1512
1133
200
image/png
Image
http://www.tellmands.in/websurvey/image/close-white.png
http/1.1
1407.1339999791
1491.3109999616
3229
2850
200
image/png
Image
http://www.tellmands.in/websurvey/image/inmoment-websurvey.png
http/1.1
1407.4859998655
1491.8259999249
3711
3332
200
image/png
Image
http://www.tellmands.in/websurvey/image/spinner.gif
http/1.1
1407.6629998162
1495.2789999079
2254
1875
200
image/gif
Image
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
http/1.1
1503.9329999126
1608.3219998982
5247
14886
200
text/html
XHR
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
http/1.1
1609.6579998266
1712.9130000249
5247
14886
200
text/html
XHR
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=f37f52f6-4b88-47d1-b3cf-5ba12b78d7e2&v=0&type=0&tag=MNSpatternBG
http/1.1
1736.091000028
1827.2189998534
1654
1205
200
image/jpeg
Image
http://www.tellmands.in/websurvey/css/webfonts/calibri-webfont.woff
http/1.1
1787.8459999338
1874.7280000243
38115
37720
200
application/x-font-woff
Font
http://www.tellmands.in/websurvey/2/detectDevice?deviceType=Mac
http/1.1
1993.7989998143
2090.2129998431
219
0
200
text/plain
XHR
http://www.tellmands.in/websurvey/2/views/policyModal.html
http/1.1
2025.1829999033
2114.5819998346
1260
2124
200
text/html
XHR
http://www.tellmands.in/websurvey/2/prompts
http/1.1
2027.2099999711
2136.0420000274
2670
5338
200
application/json
XHR
http://www.tellmands.in/websurvey/servlet/BlobServlet?s2=921fa775-f363-4e5d-9785-6c7b2f93e8e1-cd&v=0&type=1
http/1.1
2051.5799999703
2217.9270000197
3545
3091
200
image/jpeg
Image
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=7c7467d2-52b0-0d3f-87c7-81e3d35ec37b&v=0&type=0&tag=MNSheader
http/1.1
2160.3279998526
2258.629999822
20480
20033
200
image/jpeg
Image
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=5e7709b7-7f80-301d-b083-54a3dc7f0842&v=1&type=0&tag=INposEntrySpring19EN
http/1.1
2184.0909998864
2599.9859999865
171899
171434
200
image/jpeg
Image
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=d77ee9f3-d173-4050-a4ad-03b723e8fd47&v=0&type=0&tag=logo
http/1.1
2264.7049999796
2354.0619998239
6033
5590
200
image/png
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)
1004.011
9.004
1378.542
711.266
2152.025
14.269
2173.606
128.593
2314.545
11.265
2328.046
5.667
2333.734
5.41
2642.532
11.952
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 — 1.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 2.3 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.0 s
The timing of the largest text or image that is painted.

Other

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

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 900 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Tellmands.in 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://www.tellmands.in/websurvey/css/third-party.min.css
12995
70
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
26805
190
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
179703
430
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
73900
310
http://www.tellmands.in/websurvey/2/retrieveJs.js?imData=t&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
1003
110
Avoid multiple page redirects — Potential savings of 1,600 ms
Redirects can cause additional delays before the page can begin loading. Tellmands.in should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://tellmands.in/
190
http://www.tellmands.in/
190
http://www.tellmands.in/websurvey/app
70
http://www.tellmands.in/websurvey/2/begin
1150
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
0

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
http://www.tellmands.in/websurvey/css/webfonts/calibri-webfont.woff
86.882000090554
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
http://www.tellmands.in/websurvey/image/inmoment-websurvey.png
79

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of tellmands.in. 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.

ARIA

`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.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

ARIA

`[aria-*]` attributes do not match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
Failing Elements

Contrast

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.

Navigation

Some elements have 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.
Failing Elements

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.10.2
AngularJS
1.7.7
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 24 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://tellmands.in/
Allowed
http://www.tellmands.in/
Allowed
http://www.tellmands.in/websurvey/app
Allowed
http://www.tellmands.in/websurvey/2/begin
Allowed
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
Allowed
http://www.tellmands.in/websurvey/css/third-party.min.css
Allowed
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
Allowed
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
Allowed
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
Allowed
http://www.tellmands.in/websurvey/2/retrieveJs.js?imData=t&s;=inmoment_761_7649_3&_s=ce8c1571-d8aa-4481-b619-6145b5ecf079
Allowed
http://www.tellmands.in/websurvey/image/info.png
Allowed
http://www.tellmands.in/websurvey/image/remove.png
Allowed
http://www.tellmands.in/websurvey/image/close-white.png
Allowed
http://www.tellmands.in/websurvey/image/inmoment-websurvey.png
Allowed
http://www.tellmands.in/websurvey/image/spinner.gif
Allowed
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=f37f52f6-4b88-47d1-b3cf-5ba12b78d7e2&v=0&type=0&tag=MNSpatternBG
Allowed
http://www.tellmands.in/websurvey/css/webfonts/calibri-webfont.woff
Allowed
http://www.tellmands.in/websurvey/2/detectDevice?deviceType=Mac
Allowed
http://www.tellmands.in/websurvey/2/views/policyModal.html
Allowed
http://www.tellmands.in/websurvey/2/prompts
Allowed
http://www.tellmands.in/websurvey/servlet/BlobServlet?s2=921fa775-f363-4e5d-9785-6c7b2f93e8e1-cd&v=0&type=1
Allowed
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=7c7467d2-52b0-0d3f-87c7-81e3d35ec37b&v=0&type=0&tag=MNSheader
Allowed
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=5e7709b7-7f80-301d-b083-54a3dc7f0842&v=1&type=0&tag=INposEntrySpring19EN
Allowed
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=d77ee9f3-d173-4050-a4ad-03b723e8fd47&v=0&type=0&tag=logo
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 7 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
3
High

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

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
55

SEO

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

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.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Crawling and Indexing

Page is 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.
Blocking Directive Source
robots.txt is not valid — 252 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Unknown directive
3
<!--[if lte IE 7]> <html id="ng-app" ng-app="surveyApp" class="no-js lt-ie9 lt-ie8" lang="en" xml:lang="en" xmlns:ng="http://angularjs.org" xmlns="http://www.w3.org/1999/xhtml" xmlns:th="http://www.thymeleaf.org"> <![endif]-->
Unknown directive
4
<!--[if IE 8]> <html ng-app="surveyApp" class="no-js lt-ie9" lang="en" xml:lang="en" xmlns:ng="http://angularjs.org" xmlns="http://www.w3.org/1999/xhtml" xmlns:th="http://www.thymeleaf.org"> <![endif]-->
Unknown directive
5
<!--[if gt IE 8]><!--> <html ng-app="surveyApp" class="no-js notranslate" lang="en" xml:lang="en" xmlns:ng="http://angularjs.org" xmlns="http://www.w3.org/1999/xhtml" translate="no"> <!--<![endif]-->
Unknown directive
6
<head>
Syntax not understood
7
<!--[if lt IE 9]>
Syntax not understood
8
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
Unknown directive
9
<script src="app/lib/shims/ieshims.js"></script>
Syntax not understood
10
<![endif]-->
Syntax not understood
11
<!--[if lte IE 8]>
Syntax not understood
12
<script src="app/lib/angular/json3.min.js"></script>
Syntax not understood
13
<script type="text/javascript">
Syntax not understood
14
document.createElement('ng-include');
Syntax not understood
15
document.createElement('ng-pluralize');
Syntax not understood
16
document.createElement('ng-view');
Syntax not understood
17
document.createElement('ng:include');
Unknown directive
18
document.createElement('ng:pluralize');
Unknown directive
19
document.createElement('ng:view');
Unknown directive
20
</script>
Syntax not understood
21
<![endif]-->
Syntax not understood
23
<!--[if IE]>
Syntax not understood
24
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
Syntax not understood
25
<![endif]-->
Syntax not understood
27
<link id="favicon" rel="icon" type="image/png" href="/websurvey/image/faviconV2.png" />
Syntax not understood
29
<title>Marks &amp; Spencer</title>
Syntax not understood
34
<meta name="csrf-token" content="YzbUa4GsYBNAawADXsuR5jEdagw2ehf8KBCTnuXecyA=" />
Syntax not understood
35
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
Syntax not understood
36
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=2.0, user-scalable=yes" />
Syntax not understood
37
<meta name="google" content="notranslate" />
Syntax not understood
39
<meta name="robots" content="noindex,nofollow" />
Syntax not understood
44
<!-- PUTTC21, tc_web_8071 -->
Syntax not understood
45
<!-- uuid=6177677a44392b8ec83239c0 -->
Syntax not understood
52
<!-- Production resources -->
Syntax not understood
53
<link href="../css/third-party.min.css" rel="stylesheet" type="text/css" />
Syntax not understood
54
<script src="../jslib/third-party.min.js?v=761" charset="utf-8" xml:space="preserve"></script>
Unknown directive
55
<script src="../jslib/appDirectives.min.js?v=761" charset="utf-8" xml:space="preserve"></script>
Unknown directive
57
<link id="dynamic_css" rel="stylesheet" type="text/css" href="retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&amp;_s=ce8c1571-d8aa-4481-b619-6145b5ecf079" />
Syntax not understood
60
<script id="customJsEl" xml:space="preserve" src="retrieveJs.js?imData=t&s;=inmoment_761_7649_3&amp;_s=ce8c1571-d8aa-4481-b619-6145b5ecf079"></script>
Unknown directive
63
<!--[if lt IE 9]>
Syntax not understood
64
<link rel="stylesheet" type="text/css" media="all" href="../css/ws2-ie8.css"/>
Syntax not understood
65
<![endif]-->
Syntax not understood
67
<noscript><style xml:space="preserve">
Unknown directive
68
button, input, #promptArea, noscript .button { display: none }
Syntax not understood
69
@media only screen and (max-width : 800px) {
Unknown directive
70
noscript iframe{display:none;}
Unknown directive
71
noscript div{margin:.5em 0;}
Unknown directive
73
noscript .enBtn {
Syntax not understood
74
-moz-box-shadow:inset 0px 1px 0px 0px #ffffff;
Unknown directive
75
-webkit-box-shadow:inset 0px 1px 0px 0px #ffffff;
Unknown directive
76
box-shadow:inset 0px 1px 0px 0px #ffffff;
Unknown directive
77
background:-webkit-gradient( linear, left top, left bottom, color-stop(0.05, #777777), color-stop(1, #dfdfdf) );
Unknown directive
78
background:-moz-linear-gradient( center top, #777777 5%, #dfdfdf 100% );
Unknown directive
79
filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#777777', endColorstr='#dfdfdf');
Unknown directive
80
background-color:#777777;
Unknown directive
81
border:1px solid #dcdcdc;
Unknown directive
82
display:inline-block;
Unknown directive
83
color:#fff;
Unknown directive
84
font:normal bold 15px Arial;
Unknown directive
85
height:40px;
Unknown directive
86
line-height:40px;
Unknown directive
87
padding:.2em;
Unknown directive
88
text-decoration:none;
Unknown directive
89
text-align:center;
Unknown directive
90
text-shadow:1px 1px 0px #000;
Unknown directive
91
}
Syntax not understood
92
noscript .enBtn:hover {
Unknown directive
93
background:-webkit-gradient( linear, left top, left bottom, color-stop(0.05, #dfdfdf), color-stop(1, #777777) );
Unknown directive
94
background:-moz-linear-gradient( center top, #dfdfdf 5%, #777777 100% );
Unknown directive
95
filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#dfdfdf', endColorstr='#777777');
Unknown directive
96
background-color:#dfdfdf;
Unknown directive
97
}
Syntax not understood
98
noscript .enBtn:active {
Unknown directive
99
position:relative;
Unknown directive
100
top:1px;
Unknown directive
101
}
Syntax not understood
102
}
Syntax not understood
103
</style></noscript>
Syntax not understood
105
<!-- Google analytics -->
Syntax not understood
106
<script type="text/javascript" xml:space="preserve">
Unknown directive
107
var _gaq = _gaq || [];
Syntax not understood
108
_gaq.push(['_setAccount', null ]);
Syntax not understood
109
_gaq.push(['_trackPageview']);
Syntax not understood
111
if(null){
Syntax not understood
112
_gaq.push(['client._setAccount', null ]);
Syntax not understood
113
_gaq.push(['client._trackPageview']);
Syntax not understood
114
}
Syntax not understood
116
if(null){
Syntax not understood
117
(function() {
Syntax not understood
118
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
Syntax not understood
119
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
Unknown directive
120
var s = document.getElementsByTagName('script')[2];
Syntax not understood
121
s.parentNode.insertBefore(ga, s);
Syntax not understood
122
})();
Syntax not understood
123
}
Syntax not understood
124
</script>
Syntax not understood
125
<!-- ClickTale Integration -->
Syntax not understood
126
<script type="text/javascript" xml:space="preserve">
Unknown directive
127
var CTUID = null;
Syntax not understood
128
try {
Syntax not understood
129
localStorage.setItem("clickTaleUID", CTUID);
Syntax not understood
130
} catch (e) {
Syntax not understood
131
// remove this block when ClickTale URL parameter has been tested and verified.
Syntax not understood
132
console.log("Can't write clickTaleUID to localStorage");
Syntax not understood
133
}
Syntax not understood
134
var CTPartition = null;
Syntax not understood
135
var CTGUID = null;
Syntax not understood
136
if (null){
Syntax not understood
137
if(null){
Syntax not understood
138
if(null){
Syntax not understood
139
if (!window.clickTaleTagInjected) {
Syntax not understood
140
! function(d, t, u) {
Syntax not understood
141
clickTaleTagInjected = true;
Syntax not understood
142
function injectTag() {
Syntax not understood
143
var ns = d.createElementNS;
Syntax not understood
144
var a = ns ? ns.call(d, "http://www.w3.org/1999/xhtml", t) : d.createElement(t),
Unknown directive
145
s = d.getElementsByTagName(t)[0];
Syntax not understood
146
a.async = true;
Syntax not understood
147
a.crossOrigin = "anonymous";
Syntax not understood
148
a.type = "text/javascript";
Syntax not understood
149
a.src = u;
Syntax not understood
150
s.parentNode.insertBefore(a, s);
Syntax not understood
151
}
Syntax not understood
152
if (d.readyState != 'loading') {
Syntax not understood
153
injectTag();
Syntax not understood
154
} else {
Syntax not understood
155
d.addEventListener('DOMContentLoaded', function() {
Syntax not understood
156
setTimeout(injectTag, 0)
Syntax not understood
157
});
Syntax not understood
158
}
Syntax not understood
159
}(document, 'script', 'https://cdnssl.clicktale.net/' + CTPartition + '/ptc/' + CTGUID + '.js');
Unknown directive
160
}
Syntax not understood
161
}
Syntax not understood
162
}
Syntax not understood
163
}
Syntax not understood
164
</script>
Syntax not understood
165
</head>
Syntax not understood
166
<body ng-controller="surveyAppController" tabindex="-1" id="surveyApp_body" role="application" class="i_{{currentPageIndex}} page_{{currentPage().pageId}} page_identifier_{{currentPage().cssIdentifier | spaceToUnderscore}} rand_{{currentPage().randNum}} lcl_{{locale}}">
Syntax not understood
167
<div style="display:none;" ng-init="detectDevice()"></div>
Unknown directive
168
<a id="skipToContent" role="link" ng-if="wcagToggle" ng-click="skipToContent()" ng-keydown="skipToContent($event)" class="skipToContent" tabindex="1" shape="rect">{{navText['skipLink']}}</a>
Syntax not understood
171
<div id="dialog-overlay"></div>
Syntax not understood
172
<div id="dialog-box">
Syntax not understood
173
<div class="dialog-content">
Syntax not understood
174
<div id="dialog-message"></div>
Syntax not understood
175
<a href="#" id="shareExperience" class="button" onClick="shareExperience()" shape="rect">Share my experience</a>
Syntax not understood
176
<a href="#" id="noThanks" class="noThanksButton" onClick="noThanks()" shape="rect">No Thanks</a>
Syntax not understood
177
</div>
Syntax not understood
178
</div>
Syntax not understood
180
<div role="banner" ng-include=" &#39;/websurvey/2/views/policyModal.html&#39; " onload="handleGdprOnLoad()" ng-init="showGdpr=true"></div>
Syntax not understood
182
<div id="ieBanner" role="banner" ng-show="showUpdateBrowserBanner" class="surveyBanner" ng-class="{firstBanner:bothBannersSelected()}" ng-if="checkIE8()">
Unknown directive
183
<div>
Syntax not understood
184
<img src="../image/info.png" width="21" height="21" style="vertical-align: text-bottom; width:21px; height:21px;" role="img" alt="{{pageMessages.cookieBannerAltInfo}}" />
Unknown directive
185
<div id="browser_update" ng-bind-html="pageMessages.updateBrowser|unsafe"></div>
Syntax not understood
186
<a ng-class="{&#39;adaHighlight&#39;: wcagToggle}" target="_new" href="http://windows.microsoft.com/en-us/internet-explorer/download-ie" shape="rect">
Syntax not understood
187
<span ng-bind="pageMessages.updateBrowserLink"></span>
Syntax not understood
188
</a>
Syntax not understood
189
<img src="../image/remove.png" style="width:12px; height:12px; position: relative; left: 3%;" ng-class="{&#39;adaHighlight&#39;: wcagToggle}" tabindex="0" ng-keydown="spacebarKeypress($event, &#39;ieBanner&#39;)" ng-click="removeBanner()" alt="{{pageMessages.cookieBannerAltRemove}}" />
Unknown directive
190
</div>
Syntax not understood
191
</div>
Syntax not understood
192
<div id="cookieBanner" role="banner" ng-if="renderCookieBanner()" class="surveyBanner">
Syntax not understood
193
<div>
Syntax not understood
194
<img src="../image/info.png" style="vertical-align:text-bottom; width:21px; height:21px;" alt="{{pageMessages.cookieBannerAltInfo}}" />
Unknown directive
195
<span id="cookieText" ng-bind="pageMessages.cookieBannerMessage">
Syntax not understood
196
</span>
Syntax not understood
197
<a ng-class="{&#39;adaHighlight&#39;: wcagToggle}" target="_new" href="http://www.inmoment.com/privacy-policy/" shape="rect">
Syntax not understood
198
<span ng-bind="pageMessages.cookieBannerPrivacyText"></span>
Syntax not understood
199
</a>
Syntax not understood
200
<img src="../image/remove.png" style="width:12px; height:12px; position: relative; left: 3%;" ng-class="{&#39;adaHighlight&#39;: wcagToggle}" tabindex="0" ng-keydown="spacebarKeypress($event, &#39;cookieClose&#39;)" ng-click="addCookie()" role="button" alt="{{pageMessages.cookieBannerAltRemove}}" />
Unknown directive
201
</div>
Syntax not understood
202
</div>
Syntax not understood
203
<div ng-if="renderBackdropContainer()">
Syntax not understood
204
<div id="backdropContainer">
Syntax not understood
205
<iframe ng-src="{{reviewUrl}}" width="100%" height="100%" scrolling="no"></iframe>
Syntax not understood
206
<div id="backdropOverlay"></div>
Syntax not understood
207
</div>
Syntax not understood
208
</div>
Syntax not understood
209
<div ng-class="renderBackdropContainer() ? &#39;bodyContainer transferBody&#39; : &#39;bodyContainer&#39;" ng-cloak="">
Syntax not understood
210
<!-- Clear browser storage if necessary -->
Syntax not understood
212
<div style="display: none" ng-init="clearBrowserSessionStorage();"></div>
Unknown directive
215
<div role="alert" ng-if="systemError">
Syntax not understood
216
<div ng-include=" &#39;/websurvey/2/views/errors.html&#39; "></div>
Syntax not understood
217
</div>
Syntax not understood
219
<!-- Prompt Form, used for validation -->
Syntax not understood
220
<form role="form" ng-show="renderPrompts()" name="promptForm" novalidate="" id="promptForm" ng-keydown="handleEnter($event)" translate="no" method="get" enctype="application/x-www-form-urlencoded">
Syntax not understood
221
<fieldset>
Syntax not understood
222
<legend></legend>
Syntax not understood
223
<noscript aria-hidden="true">
Syntax not understood
224
<style xml:space="preserve">#spinnerOverlay {display:none;}</style>
Unknown directive
225
<iframe src="http://www.enable-javascript.com" style="width:800px;height:500px;"></iframe>
Unknown directive
226
<div><a class="enBtn" href="http://www.enable-javascript.com" target="_blank" shape="rect">Enable Javascript</a></div>
Unknown directive
227
</noscript>
Syntax not understood
229
<div role="banner" id="transferBanner" ng-if="renderBackdropContainer()">
Syntax not understood
230
<img class="banner" ng-src="{{reviewBanner}}" alt="" />
Syntax not understood
231
<a ng-href="{{reviewUrl}}" shape="rect"><img class="closer" src="../image/close-white.png" alt="{{pageMessages.cookieBannerAltClose}}" /></a>
Syntax not understood
232
</div>
Syntax not understood
235
<div id="customHeader" role="contentinfo" ng-bind-html="customHtml.header|unsafe"></div>
Syntax not understood
236
<!-- Prompt Content -->
Syntax not understood
237
<div role="contentinfo" ng-include=" &#39;app/js/content.html&#39; "></div>
Syntax not understood
239
<div id="nav" role="navigation" ng-class="{lastPageNav:surveyOver}">
Unknown directive
240
<div id="backImg"></div>
Syntax not understood
241
<div id="nextImg"></div>
Syntax not understood
242
<button aria-label="{{navText[&#39;back&#39;]}}" id="prevPageLink" type="button" ng-keydown="spacebarKeypress($event, &#39;previous&#39;)" ng-click="prevPageButtonClick($event)" ng-class="{navButton:!useNavImage(&#39;back&#39;),backNavImage:useNavImage(&#39;back&#39;),disabledNav:0&gt;=currentPageIndex}" ng-if="currentPageIndex &gt; 0" ng-hide="hideNavButtons() || hideBackButton()" ng-style="getNavSize(&#39;back&#39;)" tabindex="{{currentPage().renderedPrompts+2}}">
Syntax not understood
243
<span aria-labelledby="prevPageLink" class="arrow backArrow"></span>{{navText['back']}}
Syntax not understood
244
</button>
Syntax not understood
245
<button aria-label="{{navText[&#39;next&#39;]}}" class="g-recaptcha" data-sitekey="" data-callback="" data-action="" id="nextPageLink" type="button" ng-mousedown="nextPageMouseDown($event)" ng-keydown="spacebarKeypress($event, &#39;next&#39;)" ng-click="nextPageButtonClick($event)" ng-class="{navButton:!useNavImage(&#39;next&#39;),nextNavImage:useNavImage(&#39;next&#39;),invalidPage:pageHasErrors(promptForm,nextClickAttempts, isOnlyOfferCodeError)}" ng-hide="hideNavButtons() || hideNextButton()" ng-style="getNavSize(&#39;next&#39;)" tabindex="{{currentPage().renderedPrompts+1}}">
Syntax not understood
246
{{navText['next']}}<span aria-labelledby="nextPageLink" class="arrow nextArrow"></span>
Syntax not understood
247
</button>
Syntax not understood
248
<div id="progressBar" progressbar="" value="percentComplete" ptitle="pageMessages.progressBar"></div>
Syntax not understood
249
<div id="clear"></div> <!--IE FIX -->
Syntax not understood
250
</div>
Syntax not understood
251
<div id="footerBar" class="separatorBar"></div>
Syntax not understood
252
<div id="footer" role="contentinfo">
Syntax not understood
253
<div id="links" role="region">
Syntax not understood
254
<div class="leftLinks">
Syntax not understood
255
<span id="privacyPolicy"><a target="_blank" ng-href="{{pageMessages.privacyPolicyLink}}" tabindex="999" shape="rect"><span ng-bind="pageMessages.privacyPolicyText"></span></a></span><span class="linkSeparator">&nbsp;|</span>
Syntax not understood
256
<span ng-if="pageMessages.contestRulesLink">
Syntax not understood
257
<span id="contestRules"><a target="_blank" ng-href="{{pageMessages.contestRulesLink}}" tabindex="999" shape="rect"><span ng-bind="pageMessages.contestRulesText"></span></a></span><span class="linkSeparator">&nbsp;|</span>
Syntax not understood
258
</span>
Syntax not understood
259
<span ng-if="pageMessages.previousWinnersLink">
Syntax not understood
260
<span id="previousWinners"><a target="_blank" ng-href="{{pageMessages.previousWinnersLink}}" tabindex="999" shape="rect"><span ng-bind="pageMessages.previousWinnersText"></span></a></span><span class="linkSeparator">&nbsp;|</span>
Syntax not understood
261
</span>
Syntax not understood
262
<div id="copyright">&#169; {{currentDate | date:'yyyy'}} InMoment Inc. </div>
Syntax not understood
263
</div>
Syntax not understood
264
<div class="rightLinks">
Syntax not understood
266
<div id="companyLogo">
Syntax not understood
267
<a href="/websurvey/2/info" target="_new" tabindex="999" title="{{pageMessages.poweredByInMoment}}" shape="rect">
Syntax not understood
268
<img src="../image/inmoment-websurvey.png" alt="{{pageMessages.poweredByInMoment}}" />
Syntax not understood
269
</a>
Syntax not understood
270
</div>
Syntax not understood
271
</div>
Syntax not understood
272
</div>
Syntax not understood
273
</div>
Syntax not understood
274
<div id="customFooter" role="contentinfo" ng-bind-html="customHtml.footer|unsafe"></div>
Syntax not understood
275
<div id="transferFooter" ng-if="renderBackdropContainer()">
Syntax not understood
276
<a ng-href="{{reviewUrl}}" shape="rect">
Syntax not understood
277
Check out our OpenTell&trade; Certified Customer Reviews
Syntax not understood
278
<span class="goButton">Go</span>
Syntax not understood
279
</a>
Syntax not understood
280
</div>
Syntax not understood
281
</fieldset>
Syntax not understood
282
</form>
Syntax not understood
283
<div id="ieBackgroundImg"></div>
Syntax not understood
284
</div>
Syntax not understood
285
<div id="spinnerOverlay" ng-if="navLock" ng-style="getSpinnerOverlayHeight()">
Syntax not understood
286
<img id="pageSpinner" src="../image/spinner.gif" alt="{{pageMessages.altSpinner ? pageMessages.altSpinner : &#39;loading&#39;}}" />
Unknown directive
287
</div>
Syntax not understood
292
<div role="dialog" id="fingerprintData" ng-init="initFingerprint()" style="visibility:hidden;font-family:&#39;Sans Serif&#39;;position:absolute;left:0;top:0;overflow:hidden;width:50px;">
Unknown directive
293
<form method="get" enctype="application/x-www-form-urlencoded">
Syntax not understood
294
<input type="hidden" id="fingerprintComplete" value="false" />
Syntax not understood
295
</form>
Syntax not understood
296
</div>
Syntax not understood
299
</body>
Syntax not understood
300
</html>
Syntax not understood

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

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of tellmands.in. 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 tellmands.in 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.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
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) 54
Performance 56
Accessibility 73
Best Practices 60
SEO 58
Progressive Web App 25
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
56

Performance

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

Metrics

Total Blocking Time — 190 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).

Opportunities

Properly size images
Images can slow down the page's load time. Tellmands.in should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tellmands.in should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 6 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tellmands.in should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
26786
5827
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tellmands.in should consider minifying JS files.
Reduce unused CSS — Potential savings of 36 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tellmands.in should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
26786
24276
http://www.tellmands.in/websurvey/css/third-party.min.css
12995
12968
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 100 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
102.766
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tellmands.in 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 13 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
6527
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
6508
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 417 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
179703
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
73900
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=3973c00f-c31a-4500-857a-11d0b8a1003b&v=0&type=0&tag=INreceiptMobile
49711
http://www.tellmands.in/websurvey/css/webfonts/calibri-webfont.woff
38115
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
26786
http://www.tellmands.in/websurvey/css/third-party.min.css
12995
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=d77ee9f3-d173-4050-a4ad-03b723e8fd47&v=0&type=0&tag=logo
6033
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
5274
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
5248
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
5248
Uses efficient cache policy on static assets — 2 resources found
Tellmands.in 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://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
999999000
26786
http://www.tellmands.in/websurvey/2/retrieveJs.js?imData=t&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
999999000
984
Avoids an excessive DOM size — 119 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
119
Maximum DOM Depth
20
Maximum Child Elements
11
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Tellmands.in 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.
Keep request counts low and transfer sizes small — 25 requests • 417 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
25
427176
Script
3
254587
Image
9
73170
Stylesheet
2
39781
Font
1
38115
Other
9
16249
Document
1
5274
Media
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
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 — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.09869384765625
0.022001024199695
0.011000512099848
0.0016844534152892
0.00055002560499238
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://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
3900
1057
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
6000
211
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 tellmands.in on mobile screens.

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.

Other

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://tellmands.in/
http/1.1
0
49.028000000362
332
0
301
text/html
http://www.tellmands.in/
http/1.1
49.482000000353
131.26300000022
198
0
302
text/plain
http://www.tellmands.in/websurvey/app
http/1.1
131.7080000008
225.97700000006
548
0
302
text/html
http://www.tellmands.in/websurvey/2/begin
http/1.1
226.43000000062
381.56100000015
526
0
303
text/plain
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
http/1.1
382.01000000026
483.78100000082
5274
14970
200
text/html
Document
http://www.tellmands.in/websurvey/css/third-party.min.css
http/1.1
494.60100000033
659.63900000042
12995
104810
200
text/css
Stylesheet
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
http/1.1
494.75000000075
838.34600000046
179703
542364
200
application/javascript
Script
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
http/1.1
495.0230000004
738.89200000031
73900
304325
200
application/javascript
Script
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
http/1.1
495.16600000061
688.4170000003
26786
186639
200
text/css
Stylesheet
http://www.tellmands.in/websurvey/2/retrieveJs.js?imData=t&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
http/1.1
495.3600000008
587.99500000077
984
1128
200
application/javascript
Script
http://www.tellmands.in/websurvey/image/info.png
http/1.1
748.81300000015
834.70400000078
1521
1142
200
image/png
Image
http://www.tellmands.in/websurvey/image/remove.png
http/1.1
836.0990000001
923.1120000004
1512
1133
200
image/png
Image
http://www.tellmands.in/websurvey/image/close-white.png
http/1.1
867.00100000053
949.71000000078
3229
2850
200
image/png
Image
http://www.tellmands.in/websurvey/image/inmoment-websurvey.png
http/1.1
914.64300000007
1081.4170000003
3711
3332
200
image/png
Image
http://www.tellmands.in/websurvey/image/spinner.gif
http/1.1
914.75400000036
997.16100000023
2254
1875
200
image/gif
Image
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
http/1.1
981.01000000042
1090.1300000005
5248
14886
200
text/html
XHR
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
http/1.1
1091.273
1208.1280000002
5248
14886
200
text/html
XHR
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=f37f52f6-4b88-47d1-b3cf-5ba12b78d7e2&v=0&type=0&tag=MNSpatternBG
http/1.1
1223.8139999999
1311.0690000003
1654
1205
200
image/jpeg
Image
http://www.tellmands.in/websurvey/css/webfonts/calibri-webfont.woff
http/1.1
1244.7690000008
1416.1320000003
38115
37720
200
application/x-font-woff
Font
http://www.tellmands.in/websurvey/2/detectDevice?deviceType=AndroidPhone
http/1.1
1359.993
1453.2470000004
219
0
200
text/plain
XHR
http://www.tellmands.in/websurvey/2/views/policyModal.html
http/1.1
1379.6680000005
1465.8140000001
1260
2124
200
text/html
XHR
http://www.tellmands.in/websurvey/2/prompts
http/1.1
1381.0310000008
1492.1800000002
2670
5337
200
application/json
XHR
http://www.tellmands.in/websurvey/servlet/BlobServlet?s2=921fa775-f363-4e5d-9785-6c7b2f93e8e1-cd&v=0&type=1
http/1.1
1394.5680000006
1477.6690000008
3545
3091
200
image/jpeg
Image
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=3973c00f-c31a-4500-857a-11d0b8a1003b&v=0&type=0&tag=INreceiptMobile
http/1.1
1586.0200000006
1745.7730000006
49711
49254
200
image/png
Image
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=d77ee9f3-d173-4050-a4ad-03b723e8fd47&v=0&type=0&tag=logo
http/1.1
1598.7100000002
1685.1370000004
6033
5590
200
image/png
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)
512.907
6.216
893.855
528.481
1493.189
10.86
1520.218
105.696
1625.94
5.549
1633.454
9.285
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

Speed Index — 5.8 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 5.8 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.134
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Reduce unused JavaScript — Potential savings of 128 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://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
179703
92764
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
73900
38270
Serve images in next-gen formats — Potential savings of 32 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=3973c00f-c31a-4500-857a-11d0b8a1003b&v=0&type=0&tag=INreceiptMobile
49254
32738.85

Diagnostics

Reduce JavaScript execution time — 2.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
2776.284
2241.208
31.196
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
167.74
17.876
7.348
Unattributable
91.312
10.016
0.712
Minimize main-thread work — 3.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2276.432
Style & Layout
430.764
Other
182.08
Parse HTML & CSS
104.808
Script Parsing & Compilation
56.396
Rendering
26.304

Metrics

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

Other

Max Potential First Input Delay — 1,060 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 5.4 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 9285 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 3,150 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Tellmands.in 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://www.tellmands.in/websurvey/css/third-party.min.css
12995
330
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
26786
780
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
179703
1830
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
73900
1230
http://www.tellmands.in/websurvey/2/retrieveJs.js?imData=t&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
984
330
Avoid multiple page redirects — Potential savings of 5,280 ms
Redirects can cause additional delays before the page can begin loading. Tellmands.in should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://tellmands.in/
630
http://www.tellmands.in/
630
http://www.tellmands.in/websurvey/app
180
http://www.tellmands.in/websurvey/2/begin
3840
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
0

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
http://www.tellmands.in/websurvey/css/webfonts/calibri-webfont.woff
171.36299999947
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=d77ee9f3-d173-4050-a4ad-03b723e8fd47&v=0&type=0&tag=logo
http://www.tellmands.in/websurvey/image/inmoment-websurvey.png
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of tellmands.in. 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.

ARIA

`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.
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.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

ARIA

`[aria-*]` attributes do not match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
Failing Elements
`[role]`s do not have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Failing Elements

Contrast

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.

Navigation

Some elements have 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.
Failing Elements

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
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

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.10.2
AngularJS
1.7.7
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 23 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://tellmands.in/
Allowed
http://www.tellmands.in/
Allowed
http://www.tellmands.in/websurvey/app
Allowed
http://www.tellmands.in/websurvey/2/begin
Allowed
http://www.tellmands.in/websurvey/2/execute?_g=MTU1MzU%3DO&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
Allowed
http://www.tellmands.in/websurvey/css/third-party.min.css
Allowed
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
Allowed
http://www.tellmands.in/websurvey/jslib/appDirectives.min.js?v=761
Allowed
http://www.tellmands.in/websurvey/2/retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
Allowed
http://www.tellmands.in/websurvey/2/retrieveJs.js?imData=t&s;=inmoment_761_7649_3&_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856
Allowed
http://www.tellmands.in/websurvey/image/info.png
Allowed
http://www.tellmands.in/websurvey/image/remove.png
Allowed
http://www.tellmands.in/websurvey/image/close-white.png
Allowed
http://www.tellmands.in/websurvey/image/inmoment-websurvey.png
Allowed
http://www.tellmands.in/websurvey/image/spinner.gif
Allowed
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=f37f52f6-4b88-47d1-b3cf-5ba12b78d7e2&v=0&type=0&tag=MNSpatternBG
Allowed
http://www.tellmands.in/websurvey/css/webfonts/calibri-webfont.woff
Allowed
http://www.tellmands.in/websurvey/2/detectDevice?deviceType=AndroidPhone
Allowed
http://www.tellmands.in/websurvey/2/views/policyModal.html
Allowed
http://www.tellmands.in/websurvey/2/prompts
Allowed
http://www.tellmands.in/websurvey/servlet/BlobServlet?s2=921fa775-f363-4e5d-9785-6c7b2f93e8e1-cd&v=0&type=1
Allowed
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=3973c00f-c31a-4500-857a-11d0b8a1003b&v=0&type=0&tag=INreceiptMobile
Allowed
http://www.tellmands.in/websurvey/servlet/BlobServlet?sid=d77ee9f3-d173-4050-a4ad-03b723e8fd47&v=0&type=0&tag=logo
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 7 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
3
High

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://www.tellmands.in/websurvey/servlet/BlobServlet?sid=d77ee9f3-d173-4050-a4ad-03b723e8fd47&v=0&type=0&tag=logo
141 x 81
141 x 81
282 x 162

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

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
http://www.tellmands.in/websurvey/jslib/third-party.min.js?v=761
58

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for tellmands.in. 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 tellmands.in on mobile screens.
Document uses legible font sizes — 95.68% 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
#customFooter
2.20%
10px
.errors .errorMsg, .errors
2.12%
11px
95.68%
≥ 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 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.

Mobile Friendly

Tap targets are not sized appropriately — 57% 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
62x11
12x12

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.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Crawling and Indexing

Page is 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.
Blocking Directive Source
robots.txt is not valid — 252 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Unknown directive
3
<!--[if lte IE 7]> <html id="ng-app" ng-app="surveyApp" class="no-js lt-ie9 lt-ie8" lang="en" xml:lang="en" xmlns:ng="http://angularjs.org" xmlns="http://www.w3.org/1999/xhtml" xmlns:th="http://www.thymeleaf.org"> <![endif]-->
Unknown directive
4
<!--[if IE 8]> <html ng-app="surveyApp" class="no-js lt-ie9" lang="en" xml:lang="en" xmlns:ng="http://angularjs.org" xmlns="http://www.w3.org/1999/xhtml" xmlns:th="http://www.thymeleaf.org"> <![endif]-->
Unknown directive
5
<!--[if gt IE 8]><!--> <html ng-app="surveyApp" class="no-js notranslate" lang="en" xml:lang="en" xmlns:ng="http://angularjs.org" xmlns="http://www.w3.org/1999/xhtml" translate="no"> <!--<![endif]-->
Unknown directive
6
<head>
Syntax not understood
7
<!--[if lt IE 9]>
Syntax not understood
8
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
Unknown directive
9
<script src="app/lib/shims/ieshims.js"></script>
Syntax not understood
10
<![endif]-->
Syntax not understood
11
<!--[if lte IE 8]>
Syntax not understood
12
<script src="app/lib/angular/json3.min.js"></script>
Syntax not understood
13
<script type="text/javascript">
Syntax not understood
14
document.createElement('ng-include');
Syntax not understood
15
document.createElement('ng-pluralize');
Syntax not understood
16
document.createElement('ng-view');
Syntax not understood
17
document.createElement('ng:include');
Unknown directive
18
document.createElement('ng:pluralize');
Unknown directive
19
document.createElement('ng:view');
Unknown directive
20
</script>
Syntax not understood
21
<![endif]-->
Syntax not understood
23
<!--[if IE]>
Syntax not understood
24
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
Syntax not understood
25
<![endif]-->
Syntax not understood
27
<link id="favicon" rel="icon" type="image/png" href="/websurvey/image/faviconV2.png" />
Syntax not understood
29
<title>Marks &amp; Spencer</title>
Syntax not understood
34
<meta name="csrf-token" content="OfgaroIXwZ2MqwcQmrg2JpvSqNN8ZQql/cY31W1jSsk=" />
Syntax not understood
35
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
Syntax not understood
36
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=2.0, user-scalable=yes" />
Syntax not understood
37
<meta name="google" content="notranslate" />
Syntax not understood
39
<meta name="robots" content="noindex,nofollow" />
Syntax not understood
44
<!-- PUTTC21, tc_web_8071 -->
Syntax not understood
45
<!-- uuid=6177678a44392b8ec8323a10 -->
Syntax not understood
52
<!-- Production resources -->
Syntax not understood
53
<link href="../css/third-party.min.css" rel="stylesheet" type="text/css" />
Syntax not understood
54
<script src="../jslib/third-party.min.js?v=761" charset="utf-8" xml:space="preserve"></script>
Unknown directive
55
<script src="../jslib/appDirectives.min.js?v=761" charset="utf-8" xml:space="preserve"></script>
Unknown directive
57
<link id="dynamic_css" rel="stylesheet" type="text/css" href="retrieveCss.css?themeId=7649&s;=inmoment_761_7649_3&amp;_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856" />
Syntax not understood
60
<script id="customJsEl" xml:space="preserve" src="retrieveJs.js?imData=t&s;=inmoment_761_7649_3&amp;_s=78c80ad4-f3f0-48f6-8dfe-ac400e227856"></script>
Unknown directive
63
<!--[if lt IE 9]>
Syntax not understood
64
<link rel="stylesheet" type="text/css" media="all" href="../css/ws2-ie8.css"/>
Syntax not understood
65
<![endif]-->
Syntax not understood
67
<noscript><style xml:space="preserve">
Unknown directive
68
button, input, #promptArea, noscript .button { display: none }
Syntax not understood
69
@media only screen and (max-width : 800px) {
Unknown directive
70
noscript iframe{display:none;}
Unknown directive
71
noscript div{margin:.5em 0;}
Unknown directive
73
noscript .enBtn {
Syntax not understood
74
-moz-box-shadow:inset 0px 1px 0px 0px #ffffff;
Unknown directive
75
-webkit-box-shadow:inset 0px 1px 0px 0px #ffffff;
Unknown directive
76
box-shadow:inset 0px 1px 0px 0px #ffffff;
Unknown directive
77
background:-webkit-gradient( linear, left top, left bottom, color-stop(0.05, #777777), color-stop(1, #dfdfdf) );
Unknown directive
78
background:-moz-linear-gradient( center top, #777777 5%, #dfdfdf 100% );
Unknown directive
79
filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#777777', endColorstr='#dfdfdf');
Unknown directive
80
background-color:#777777;
Unknown directive
81
border:1px solid #dcdcdc;
Unknown directive
82
display:inline-block;
Unknown directive
83
color:#fff;
Unknown directive
84
font:normal bold 15px Arial;
Unknown directive
85
height:40px;
Unknown directive
86
line-height:40px;
Unknown directive
87
padding:.2em;
Unknown directive
88
text-decoration:none;
Unknown directive
89
text-align:center;
Unknown directive
90
text-shadow:1px 1px 0px #000;
Unknown directive
91
}
Syntax not understood
92
noscript .enBtn:hover {
Unknown directive
93
background:-webkit-gradient( linear, left top, left bottom, color-stop(0.05, #dfdfdf), color-stop(1, #777777) );
Unknown directive
94
background:-moz-linear-gradient( center top, #dfdfdf 5%, #777777 100% );
Unknown directive
95
filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#dfdfdf', endColorstr='#777777');
Unknown directive
96
background-color:#dfdfdf;
Unknown directive
97
}
Syntax not understood
98
noscript .enBtn:active {
Unknown directive
99
position:relative;
Unknown directive
100
top:1px;
Unknown directive
101
}
Syntax not understood
102
}
Syntax not understood
103
</style></noscript>
Syntax not understood
105
<!-- Google analytics -->
Syntax not understood
106
<script type="text/javascript" xml:space="preserve">
Unknown directive
107
var _gaq = _gaq || [];
Syntax not understood
108
_gaq.push(['_setAccount', null ]);
Syntax not understood
109
_gaq.push(['_trackPageview']);
Syntax not understood
111
if(null){
Syntax not understood
112
_gaq.push(['client._setAccount', null ]);
Syntax not understood
113
_gaq.push(['client._trackPageview']);
Syntax not understood
114
}
Syntax not understood
116
if(null){
Syntax not understood
117
(function() {
Syntax not understood
118
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
Syntax not understood
119
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
Unknown directive
120
var s = document.getElementsByTagName('script')[2];
Syntax not understood
121
s.parentNode.insertBefore(ga, s);
Syntax not understood
122
})();
Syntax not understood
123
}
Syntax not understood
124
</script>
Syntax not understood
125
<!-- ClickTale Integration -->
Syntax not understood
126
<script type="text/javascript" xml:space="preserve">
Unknown directive
127
var CTUID = null;
Syntax not understood
128
try {
Syntax not understood
129
localStorage.setItem("clickTaleUID", CTUID);
Syntax not understood
130
} catch (e) {
Syntax not understood
131
// remove this block when ClickTale URL parameter has been tested and verified.
Syntax not understood
132
console.log("Can't write clickTaleUID to localStorage");
Syntax not understood
133
}
Syntax not understood
134
var CTPartition = null;
Syntax not understood
135
var CTGUID = null;
Syntax not understood
136
if (null){
Syntax not understood
137
if(null){
Syntax not understood
138
if(null){
Syntax not understood
139
if (!window.clickTaleTagInjected) {
Syntax not understood
140
! function(d, t, u) {
Syntax not understood
141
clickTaleTagInjected = true;
Syntax not understood
142
function injectTag() {
Syntax not understood
143
var ns = d.createElementNS;
Syntax not understood
144
var a = ns ? ns.call(d, "http://www.w3.org/1999/xhtml", t) : d.createElement(t),
Unknown directive
145
s = d.getElementsByTagName(t)[0];
Syntax not understood
146
a.async = true;
Syntax not understood
147
a.crossOrigin = "anonymous";
Syntax not understood
148
a.type = "text/javascript";
Syntax not understood
149
a.src = u;
Syntax not understood
150
s.parentNode.insertBefore(a, s);
Syntax not understood
151
}
Syntax not understood
152
if (d.readyState != 'loading') {
Syntax not understood
153
injectTag();
Syntax not understood
154
} else {
Syntax not understood
155
d.addEventListener('DOMContentLoaded', function() {
Syntax not understood
156
setTimeout(injectTag, 0)
Syntax not understood
157
});
Syntax not understood
158
}
Syntax not understood
159
}(document, 'script', 'https://cdnssl.clicktale.net/' + CTPartition + '/ptc/' + CTGUID + '.js');
Unknown directive
160
}
Syntax not understood
161
}
Syntax not understood
162
}
Syntax not understood
163
}
Syntax not understood
164
</script>
Syntax not understood
165
</head>
Syntax not understood
166
<body ng-controller="surveyAppController" tabindex="-1" id="surveyApp_body" role="application" class="i_{{currentPageIndex}} page_{{currentPage().pageId}} page_identifier_{{currentPage().cssIdentifier | spaceToUnderscore}} rand_{{currentPage().randNum}} lcl_{{locale}}">
Syntax not understood
167
<div style="display:none;" ng-init="detectDevice()"></div>
Unknown directive
168
<a id="skipToContent" role="link" ng-if="wcagToggle" ng-click="skipToContent()" ng-keydown="skipToContent($event)" class="skipToContent" tabindex="1" shape="rect">{{navText['skipLink']}}</a>
Syntax not understood
171
<div id="dialog-overlay"></div>
Syntax not understood
172
<div id="dialog-box">
Syntax not understood
173
<div class="dialog-content">
Syntax not understood
174
<div id="dialog-message"></div>
Syntax not understood
175
<a href="#" id="shareExperience" class="button" onClick="shareExperience()" shape="rect">Share my experience</a>
Syntax not understood
176
<a href="#" id="noThanks" class="noThanksButton" onClick="noThanks()" shape="rect">No Thanks</a>
Syntax not understood
177
</div>
Syntax not understood
178
</div>
Syntax not understood
180
<div role="banner" ng-include=" &#39;/websurvey/2/views/policyModal.html&#39; " onload="handleGdprOnLoad()" ng-init="showGdpr=true"></div>
Syntax not understood
182
<div id="ieBanner" role="banner" ng-show="showUpdateBrowserBanner" class="surveyBanner" ng-class="{firstBanner:bothBannersSelected()}" ng-if="checkIE8()">
Unknown directive
183
<div>
Syntax not understood
184
<img src="../image/info.png" width="21" height="21" style="vertical-align: text-bottom; width:21px; height:21px;" role="img" alt="{{pageMessages.cookieBannerAltInfo}}" />
Unknown directive
185
<div id="browser_update" ng-bind-html="pageMessages.updateBrowser|unsafe"></div>
Syntax not understood
186
<a ng-class="{&#39;adaHighlight&#39;: wcagToggle}" target="_new" href="http://windows.microsoft.com/en-us/internet-explorer/download-ie" shape="rect">
Syntax not understood
187
<span ng-bind="pageMessages.updateBrowserLink"></span>
Syntax not understood
188
</a>
Syntax not understood
189
<img src="../image/remove.png" style="width:12px; height:12px; position: relative; left: 3%;" ng-class="{&#39;adaHighlight&#39;: wcagToggle}" tabindex="0" ng-keydown="spacebarKeypress($event, &#39;ieBanner&#39;)" ng-click="removeBanner()" alt="{{pageMessages.cookieBannerAltRemove}}" />
Unknown directive
190
</div>
Syntax not understood
191
</div>
Syntax not understood
192
<div id="cookieBanner" role="banner" ng-if="renderCookieBanner()" class="surveyBanner">
Syntax not understood
193
<div>
Syntax not understood
194
<img src="../image/info.png" style="vertical-align:text-bottom; width:21px; height:21px;" alt="{{pageMessages.cookieBannerAltInfo}}" />
Unknown directive
195
<span id="cookieText" ng-bind="pageMessages.cookieBannerMessage">
Syntax not understood
196
</span>
Syntax not understood
197
<a ng-class="{&#39;adaHighlight&#39;: wcagToggle}" target="_new" href="http://www.inmoment.com/privacy-policy/" shape="rect">
Syntax not understood
198
<span ng-bind="pageMessages.cookieBannerPrivacyText"></span>
Syntax not understood
199
</a>
Syntax not understood
200
<img src="../image/remove.png" style="width:12px; height:12px; position: relative; left: 3%;" ng-class="{&#39;adaHighlight&#39;: wcagToggle}" tabindex="0" ng-keydown="spacebarKeypress($event, &#39;cookieClose&#39;)" ng-click="addCookie()" role="button" alt="{{pageMessages.cookieBannerAltRemove}}" />
Unknown directive
201
</div>
Syntax not understood
202
</div>
Syntax not understood
203
<div ng-if="renderBackdropContainer()">
Syntax not understood
204
<div id="backdropContainer">
Syntax not understood
205
<iframe ng-src="{{reviewUrl}}" width="100%" height="100%" scrolling="no"></iframe>
Syntax not understood
206
<div id="backdropOverlay"></div>
Syntax not understood
207
</div>
Syntax not understood
208
</div>
Syntax not understood
209
<div ng-class="renderBackdropContainer() ? &#39;bodyContainer transferBody&#39; : &#39;bodyContainer&#39;" ng-cloak="">
Syntax not understood
210
<!-- Clear browser storage if necessary -->
Syntax not understood
212
<div style="display: none" ng-init="clearBrowserSessionStorage();"></div>
Unknown directive
215
<div role="alert" ng-if="systemError">
Syntax not understood
216
<div ng-include=" &#39;/websurvey/2/views/errors.html&#39; "></div>
Syntax not understood
217
</div>
Syntax not understood
219
<!-- Prompt Form, used for validation -->
Syntax not understood
220
<form role="form" ng-show="renderPrompts()" name="promptForm" novalidate="" id="promptForm" ng-keydown="handleEnter($event)" translate="no" method="get" enctype="application/x-www-form-urlencoded">
Syntax not understood
221
<fieldset>
Syntax not understood
222
<legend></legend>
Syntax not understood
223
<noscript aria-hidden="true">
Syntax not understood
224
<style xml:space="preserve">#spinnerOverlay {display:none;}</style>
Unknown directive
225
<iframe src="http://www.enable-javascript.com" style="width:800px;height:500px;"></iframe>
Unknown directive
226
<div><a class="enBtn" href="http://www.enable-javascript.com" target="_blank" shape="rect">Enable Javascript</a></div>
Unknown directive
227
</noscript>
Syntax not understood
229
<div role="banner" id="transferBanner" ng-if="renderBackdropContainer()">
Syntax not understood
230
<img class="banner" ng-src="{{reviewBanner}}" alt="" />
Syntax not understood
231
<a ng-href="{{reviewUrl}}" shape="rect"><img class="closer" src="../image/close-white.png" alt="{{pageMessages.cookieBannerAltClose}}" /></a>
Syntax not understood
232
</div>
Syntax not understood
235
<div id="customHeader" role="contentinfo" ng-bind-html="customHtml.header|unsafe"></div>
Syntax not understood
236
<!-- Prompt Content -->
Syntax not understood
237
<div role="contentinfo" ng-include=" &#39;app/js/content.html&#39; "></div>
Syntax not understood
239
<div id="nav" role="navigation" ng-class="{lastPageNav:surveyOver}">
Unknown directive
240
<div id="backImg"></div>
Syntax not understood
241
<div id="nextImg"></div>
Syntax not understood
242
<button aria-label="{{navText[&#39;back&#39;]}}" id="prevPageLink" type="button" ng-keydown="spacebarKeypress($event, &#39;previous&#39;)" ng-click="prevPageButtonClick($event)" ng-class="{navButton:!useNavImage(&#39;back&#39;),backNavImage:useNavImage(&#39;back&#39;),disabledNav:0&gt;=currentPageIndex}" ng-if="currentPageIndex &gt; 0" ng-hide="hideNavButtons() || hideBackButton()" ng-style="getNavSize(&#39;back&#39;)" tabindex="{{currentPage().renderedPrompts+2}}">
Syntax not understood
243
<span aria-labelledby="prevPageLink" class="arrow backArrow"></span>{{navText['back']}}
Syntax not understood
244
</button>
Syntax not understood
245
<button aria-label="{{navText[&#39;next&#39;]}}" class="g-recaptcha" data-sitekey="" data-callback="" data-action="" id="nextPageLink" type="button" ng-mousedown="nextPageMouseDown($event)" ng-keydown="spacebarKeypress($event, &#39;next&#39;)" ng-click="nextPageButtonClick($event)" ng-class="{navButton:!useNavImage(&#39;next&#39;),nextNavImage:useNavImage(&#39;next&#39;),invalidPage:pageHasErrors(promptForm,nextClickAttempts, isOnlyOfferCodeError)}" ng-hide="hideNavButtons() || hideNextButton()" ng-style="getNavSize(&#39;next&#39;)" tabindex="{{currentPage().renderedPrompts+1}}">
Syntax not understood
246
{{navText['next']}}<span aria-labelledby="nextPageLink" class="arrow nextArrow"></span>
Syntax not understood
247
</button>
Syntax not understood
248
<div id="progressBar" progressbar="" value="percentComplete" ptitle="pageMessages.progressBar"></div>
Syntax not understood
249
<div id="clear"></div> <!--IE FIX -->
Syntax not understood
250
</div>
Syntax not understood
251
<div id="footerBar" class="separatorBar"></div>
Syntax not understood
252
<div id="footer" role="contentinfo">
Syntax not understood
253
<div id="links" role="region">
Syntax not understood
254
<div class="leftLinks">
Syntax not understood
255
<span id="privacyPolicy"><a target="_blank" ng-href="{{pageMessages.privacyPolicyLink}}" tabindex="999" shape="rect"><span ng-bind="pageMessages.privacyPolicyText"></span></a></span><span class="linkSeparator">&nbsp;|</span>
Syntax not understood
256
<span ng-if="pageMessages.contestRulesLink">
Syntax not understood
257
<span id="contestRules"><a target="_blank" ng-href="{{pageMessages.contestRulesLink}}" tabindex="999" shape="rect"><span ng-bind="pageMessages.contestRulesText"></span></a></span><span class="linkSeparator">&nbsp;|</span>
Syntax not understood
258
</span>
Syntax not understood
259
<span ng-if="pageMessages.previousWinnersLink">
Syntax not understood
260
<span id="previousWinners"><a target="_blank" ng-href="{{pageMessages.previousWinnersLink}}" tabindex="999" shape="rect"><span ng-bind="pageMessages.previousWinnersText"></span></a></span><span class="linkSeparator">&nbsp;|</span>
Syntax not understood
261
</span>
Syntax not understood
262
<div id="copyright">&#169; {{currentDate | date:'yyyy'}} InMoment Inc. </div>
Syntax not understood
263
</div>
Syntax not understood
264
<div class="rightLinks">
Syntax not understood
266
<div id="companyLogo">
Syntax not understood
267
<a href="/websurvey/2/info" target="_new" tabindex="999" title="{{pageMessages.poweredByInMoment}}" shape="rect">
Syntax not understood
268
<img src="../image/inmoment-websurvey.png" alt="{{pageMessages.poweredByInMoment}}" />
Syntax not understood
269
</a>
Syntax not understood
270
</div>
Syntax not understood
271
</div>
Syntax not understood
272
</div>
Syntax not understood
273
</div>
Syntax not understood
274
<div id="customFooter" role="contentinfo" ng-bind-html="customHtml.footer|unsafe"></div>
Syntax not understood
275
<div id="transferFooter" ng-if="renderBackdropContainer()">
Syntax not understood
276
<a ng-href="{{reviewUrl}}" shape="rect">
Syntax not understood
277
Check out our OpenTell&trade; Certified Customer Reviews
Syntax not understood
278
<span class="goButton">Go</span>
Syntax not understood
279
</a>
Syntax not understood
280
</div>
Syntax not understood
281
</fieldset>
Syntax not understood
282
</form>
Syntax not understood
283
<div id="ieBackgroundImg"></div>
Syntax not understood
284
</div>
Syntax not understood
285
<div id="spinnerOverlay" ng-if="navLock" ng-style="getSpinnerOverlayHeight()">
Syntax not understood
286
<img id="pageSpinner" src="../image/spinner.gif" alt="{{pageMessages.altSpinner ? pageMessages.altSpinner : &#39;loading&#39;}}" />
Unknown directive
287
</div>
Syntax not understood
292
<div role="dialog" id="fingerprintData" ng-init="initFingerprint()" style="visibility:hidden;font-family:&#39;Sans Serif&#39;;position:absolute;left:0;top:0;overflow:hidden;width:50px;">
Unknown directive
293
<form method="get" enctype="application/x-www-form-urlencoded">
Syntax not understood
294
<input type="hidden" id="fingerprintComplete" value="false" />
Syntax not understood
295
</form>
Syntax not understood
296
</div>
Syntax not understood
299
</body>
Syntax not understood
300
</html>
Syntax not understood

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

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of tellmands.in. 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 tellmands.in 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.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
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: 3.33.152.147
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
Amazon Technologies 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

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
tellmands.in. 15.197.142.173 IN 600
tellmands.in. 3.33.152.147 IN 600

NS Records

Host Nameserver Class TTL
tellmands.in. pdns07.domaincontrol.com. IN 3600
tellmands.in. pdns08.domaincontrol.com. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
tellmands.in. pdns07.domaincontrol.com. dns.jomax.net. 600

TXT Records

Host Value Class TTL
tellmands.in. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code:

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: pdns07.domaincontrol.com
pdns08.domaincontrol.com
Full Whois:

Nameservers

Name IP Address
pdns07.domaincontrol.com 97.74.111.53
pdns08.domaincontrol.com 173.201.79.53
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

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

Sites hosted on the same IP address

Domain Valuation Snoop Score
$570 USD 2/5
0/5
$3,434 USD 2/5
$1,930 USD 2/5