howwasyourday.com

howwasyourday.com may not be SSL secured

Free website and domain report on howwasyourday.com

Last Updated: 12th May, 2020 Update Now
Overview

Snoop Summary for howwasyourday.com

This is a free and comprehensive report about howwasyourday.com. The domain howwasyourday.com is currently hosted on a server located in Dallas, Texas in United States with the IP address 45.33.23.183, where the local currency is USD and English is the local language. If howwasyourday.com was to be sold it would possibly be worth $287 USD (based on the daily revenue potential of the website over a 24 month period). Howwasyourday.com receives an estimated 133 unique visitors every day - a decent amount of traffic! This report was last updated 12th May, 2020.

About howwasyourday.com

Site Preview: howwasyourday.com
Title:
Description:
Keywords and Tags: parked domain
Related Terms:
Fav Icon:
Age: Over 21 years old
Domain Created: 4th October, 2002
Domain Updated: 18th January, 2019
Domain Expires: 4th October, 2020
Review

Snoop Score

1/5

Valuation

$287 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,620,152
Alexa Reach: <0.0001%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 133
Monthly Visitors: 4,048
Yearly Visitors: 48,545
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $12 USD
Yearly Revenue: $138 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: howwasyourday.com 17
Domain Name: howwasyourday 13
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 62
Performance 0
Accessibility 40
Best Practices 69
SEO 78
Progressive Web App 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
0

Performance

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

Opportunities

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 100 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.

Diagnostics

Avoids enormous network payloads — Total size was 575 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://static.uniregistry.com/assets/img/landing-pages/bg-parking.jpg
304045
https://static.uniregistry.com/assets/fonts/proxima-nova/2191FE_4_0.woff
65276
https://www.google.com/adsense/domains/caf.js
60161
http://www.google.com/adsense/domains/caf.js
58574
http://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js
30573
http://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js
30573
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-nameadmin01_js&hl=en&swp=as-drid-oo-1705318292312488&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300165%2C17300167%2C17300178%2C17300194%2C17300196&format=s%7Cr10&num=0&output=afd_ads&domain_name=www2.howwasyourday.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1589305834634&u_w=800&u_h=600&biw=1350&bih=940&isw=1348&ish=940&psw=1348&psh=394&frm=1&uio=sd16sv16ff2fa2sa16sl1sr1--st20&cont=rs&csize=w620h0&inames=slave-1-1&jsv=27311&rurl=http%3A%2F%2Fwww2.howwasyourday.com%2Fsearch_caf.php%3Fuid%3Dwww25ebae1e9e831d0.01960402%26src%3Dmountains%26abp%3D1%26country%3DUS&referer=http%3A%2F%2Fwww2.howwasyourday.com%2F
7737
http://www2.howwasyourday.com/search_caf.php?uid=www25ebae1e9e831d0.01960402&src=mountains&abp=1&country=US
6197
https://www.google.com/js/bg/hoakTGSdv_jI8DI7b71Hu182_w1HnQYnfKWqXl6Cy2E.js
6104
https://www.google.com/js/bg/hoakTGSdv_jI8DI7b71Hu182_w1HnQYnfKWqXl6Cy2E.js
6104
Avoids an excessive DOM size — 3 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
3
Maximum DOM Depth
2
Maximum Child Elements
3
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Howwasyourday.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Keep request counts low and transfer sizes small — 24 requests • 575 KB
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
24
589063
Image
6
310352
Script
8
193015
Font
1
65276
Document
8
19795
Other
1
625
Stylesheet
0
0
Media
0
0
Third-party
14
577076

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.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://howwasyourday.com/
0
95.05799994804
1729
1519
200
text/html
Document
http://howwasyourday.com/mtm/async/eyJ1cmkiOiIvIiwiYXJncyI6IiIsInJlZmVyZXIiOiIifQ:1jYZ33:WfVz0UZryK23P0m0BALUPnvKNys/1
105.36899999715
194.20600007288
625
30
200
text/html
Fetch
http://www2.howwasyourday.com/
197.50400003977
199.17399995029
0
0
-1
Document
http://www2.howwasyourday.com/
201.29300002009
455.98099986091
1425
2378
200
text/html
Document
http://return.uk.uniregistry.com/return_js.php?d=howwasyourday.com&s=1589305833
466.17099992
678.17600001581
422
32
200
application/javascript
Script
http://www2.howwasyourday.com/ads.js
466.4000000339
711.35300002061
504
128
200
application/javascript
Script
http://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js
466.60499996506
473.46900007688
30573
85925
200
text/javascript
Script
http://www2.howwasyourday.com/tg.php?uid=www25ebae1e9e831d0.01960402
737.93299985118
966.14499995485
551
348
200
text/html
Document
http://www2.howwasyourday.com/search_caf.php?uid=www25ebae1e9e831d0.01960402&src=mountains&abp=1&country=US
738.8829998672
972.35799999908
6197
19197
200
text/html
Document
http://www2.howwasyourday.com/page.php?www25ebae1e9e831d0.01960402
740.48099992797
945.40499988943
438
177
200
text/html
Document
http://www2.howwasyourday.com/img.php?www25ebae1e9e831d0.01960402
955.8089999482
1162.2709999792
259
43
200
image/gif
Image
http://www2.howwasyourday.com/track.php?uid=www25ebae1e9e831d0.01960402&d=howwasyourday.com&sr=800x600
979.34499988332
1201.653999975
259
43
200
image/gif
Image
http://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js
988.55899996124
988.66000003181
30573
85925
200
text/javascript
Script
http://www.google.com/adsense/domains/caf.js
989.88700006157
1008.9249999728
58574
165601
200
text/javascript
Script
https://static.uniregistry.com/assets/img/ur-logo-white.png
990.13999989256
1043.7149999198
4057
3578
200
image/png
Image
http://www.gstatic.com/domainads/tracking/partner.gif?ts=1589305834585&rid=5102392
1011.4670000039
1017.8979998454
380
43
200
image/gif
Image
https://static.uniregistry.com/assets/img/landing-pages/bg-parking.jpg
1037.7539999317
1117.9760000668
304045
303563
200
image/jpeg
Image
https://static.uniregistry.com/assets/fonts/proxima-nova/2191FE_4_0.woff
1038.6230000295
1263.1190000102
65276
64678
200
application/font-woff
Font
https://www.google.com/afs/ads/i/iframe.html
1068.1600000244
1073.8259998616
1718
1243
200
text/html
Document
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-nameadmin01_js&hl=en&swp=as-drid-oo-1705318292312488&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300165%2C17300167%2C17300178%2C17300194%2C17300196&format=s%7Cr10&num=0&output=afd_ads&domain_name=www2.howwasyourday.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1589305834634&u_w=800&u_h=600&biw=1350&bih=940&isw=1348&ish=940&psw=1348&psh=394&frm=1&uio=sd16sv16ff2fa2sa16sl1sr1--st20&cont=rs&csize=w620h0&inames=slave-1-1&jsv=27311&rurl=http%3A%2F%2Fwww2.howwasyourday.com%2Fsearch_caf.php%3Fuid%3Dwww25ebae1e9e831d0.01960402%26src%3Dmountains%26abp%3D1%26country%3DUS&referer=http%3A%2F%2Fwww2.howwasyourday.com%2F
1073.7069998868
1173.5409998801
7737
10432
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
1185.7819999568
1207.3579998687
60161
165541
200
text/javascript
Script
https://afs.googleusercontent.com/dp-nameadmin/chevron-gray.png
1265.3719999362
1269.5269999094
1352
767
200
image/png
Image
https://www.google.com/js/bg/hoakTGSdv_jI8DI7b71Hu182_w1HnQYnfKWqXl6Cy2E.js
1293.5629999265
1297.7729998529
6104
12464
200
text/javascript
Script
https://www.google.com/js/bg/hoakTGSdv_jI8DI7b71Hu182_w1HnQYnfKWqXl6Cy2E.js
1300.212000031
1304.0299999993
6104
12464
200
text/javascript
Script
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.

Metrics

First Contentful Paint
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint
The time taken for the primary content of the page to be rendered.
Speed Index
The time taken for the page contents to be visibly populated.
Time to Interactive
The time taken for the page to become fully interactive.
First CPU Idle
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive howwasyourday.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Diagnostics
Below is a collection of useful page vitals.
Metrics
Below is a collection of metrics.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Howwasyourday.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Howwasyourday.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Howwasyourday.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Howwasyourday.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Howwasyourday.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Howwasyourday.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Howwasyourday.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Howwasyourday.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Serve static assets with an efficient cache policy — 8 resources found
Howwasyourday.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
http://www2.howwasyourday.com/ads.js
0
504
http://return.uk.uniregistry.com/return_js.php?d=howwasyourday.com&s=1589305833
0
422
http://www2.howwasyourday.com/img.php?www25ebae1e9e831d0.01960402
0
259
http://www2.howwasyourday.com/track.php?uid=www25ebae1e9e831d0.01960402&d=howwasyourday.com&sr=800x600
0
259
https://afs.googleusercontent.com/dp-nameadmin/chevron-gray.png
82800000
1352
https://static.uniregistry.com/assets/img/landing-pages/bg-parking.jpg
86400000
304045
https://static.uniregistry.com/assets/fonts/proxima-nova/2191FE_4_0.woff
86400000
65276
https://static.uniregistry.com/assets/img/ur-logo-white.png
86400000
4057
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Minimizes main-thread work
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.
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)
https://static.uniregistry.com/assets/fonts/proxima-nova/2191FE_4_0.woff
224.49599998072
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.
40

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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-*]` 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.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Howwasyourday.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Howwasyourday.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Howwasyourday.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
69

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.5.2
jQuery (Fast path)
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 13 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
http://howwasyourday.com/
http://howwasyourday.com/mtm/async/eyJ1cmkiOiIvIiwiYXJncyI6IiIsInJlZmVyZXIiOiIifQ:1jYZ33:WfVz0UZryK23P0m0BALUPnvKNys/1
http://www2.howwasyourday.com/
http://return.uk.uniregistry.com/return_js.php?d=howwasyourday.com&s=1589305833
http://www2.howwasyourday.com/ads.js
http://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js
http://www2.howwasyourday.com/tg.php?uid=www25ebae1e9e831d0.01960402
http://www2.howwasyourday.com/search_caf.php?uid=www25ebae1e9e831d0.01960402&src=mountains&abp=1&country=US
http://www2.howwasyourday.com/page.php?www25ebae1e9e831d0.01960402
http://www2.howwasyourday.com/img.php?www25ebae1e9e831d0.01960402
http://www2.howwasyourday.com/track.php?uid=www25ebae1e9e831d0.01960402&d=howwasyourday.com&sr=800x600
http://www.google.com/adsense/domains/caf.js
http://www.gstatic.com/domainads/tracking/partner.gif?ts=1589305834585&rid=5102392
Uses `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.
URL Location
http://www2.howwasyourday.com/page.php?www25ebae1e9e831d0.01960402
line: 6
http://www2.howwasyourday.com/tg.php?uid=www25ebae1e9e831d0.01960402
line: 12
http://www2.howwasyourday.com/search_caf.php?uid=www25ebae1e9e831d0.01960402&src=mountains&abp=1&country=US
line: 71
https://www.google.com/adsense/domains/caf.js
line: 193
Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Includes front-end JavaScript libraries with known security vulnerabilities — 4 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
78

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

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

Content Best Practices

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

Manual Checks

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

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 13 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
http://howwasyourday.com/
http://howwasyourday.com/mtm/async/eyJ1cmkiOiIvIiwiYXJncyI6IiIsInJlZmVyZXIiOiIifQ:1jYZ33:WfVz0UZryK23P0m0BALUPnvKNys/1
http://www2.howwasyourday.com/
http://return.uk.uniregistry.com/return_js.php?d=howwasyourday.com&s=1589305833
http://www2.howwasyourday.com/ads.js
http://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js
http://www2.howwasyourday.com/tg.php?uid=www25ebae1e9e831d0.01960402
http://www2.howwasyourday.com/search_caf.php?uid=www25ebae1e9e831d0.01960402&src=mountains&abp=1&country=US
http://www2.howwasyourday.com/page.php?www25ebae1e9e831d0.01960402
http://www2.howwasyourday.com/img.php?www25ebae1e9e831d0.01960402
http://www2.howwasyourday.com/track.php?uid=www25ebae1e9e831d0.01960402&d=howwasyourday.com&sr=800x600
http://www.google.com/adsense/domains/caf.js
http://www.gstatic.com/domainads/tracking/partner.gif?ts=1589305834585&rid=5102392
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of howwasyourday.com on mobile screens.
Does not provide fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 71
Performance 90
Accessibility 72
Best Practices 85
SEO 73
Progressive Web App 37
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
90

Performance

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

Metrics

First Contentful Paint — 2.2 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 2.2 s
The time taken for the primary content of the page to be rendered.
Speed Index — 2.2 s
The time taken for the page contents to be visibly populated.

Other

Estimated Input Latency — 50 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive howwasyourday.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://howwasyourday.com/
0
73.49099998828
1729
1519
200
text/html
Document
http://howwasyourday.com/mtm/async/eyJ1cmkiOiIvIiwiYXJncyI6IiIsInJlZmVyZXIiOiIifQ:1jYZ3B:I4jsZzmF8aEYm7N6-0a12V8SRsY/1
84.452000039164
191.11100002192
733
87
200
text/html
Fetch
http://www6.howwasyourday.com/?s_token=1589305841.5030060368&uuid=1589305841.5030060368
193.96100001177
195.18500001868
0
0
-1
Document
http://www6.howwasyourday.com/?s_token=1589305841.5030060368&uuid=1589305841.5030060368
196.86600001296
226.93599999184
1363
800
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
235.77700002352
265.81400004216
60275
165617
200
text/javascript
Script
https://d1hi41nc56pmug.cloudfront.net/static/js/main.e38721e2.js
235.90999998851
337.079000019
94603
299502
200
application/javascript
Script
https://api.aws.parking.godaddy.com/v1/domains/www6.howwasyourday.com/landerParams
406.00900002755
439.812000026
293
0
200
Fetch
https://api.aws.parking.godaddy.com/v1/domains/www6.howwasyourday.com/landerParams
440.90300000971
480.8390000253
1551
1317
200
application/json
Fetch
https://www.google.com/dp/ads?r=m&domain_name=howwasyourday.com&cpp=0&client=dp-namemedia01&channel=00001&adtest=off&adsafe=low&type=3&pcsa=false&psid=3767353295&swp=as-drid-oo-1502969727449347&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300169%2C17300171%2C17300194%2C17300196&format=r6&num=0&output=afd_ads&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1589305841831&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=157&frm=0&uio=st24sa11lt40sl1sr1-&cont=relatedLinks&csize=w412h18&inames=master-1&jsv=27311&rurl=http%3A%2F%2Fwww6.howwasyourday.com%2F%3Fs_token%3D1589305841.5030060368%26uuid%3D1589305841.5030060368&referer=http%3A%2F%2Fhowwasyourday.com%2F
507.46600003913
613.3109999937
7593
9715
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
623.73699998716
640.95900004031
59949
165577
200
text/javascript
Script
https://afs.googleusercontent.com/dp-namemedia/bullet-arrows-orange.png
677.88900004234
680.83299999125
1121
564
200
image/png
Image
https://api.aws.parking.godaddy.com/v1/parkingEvents
683.8829999906
705.79199999338
237
0
200
text/plain
Fetch
https://api.parking.godaddy.com/v1/parkingEvents
684.35600004159
749.55100001534
246
0
200
text/plain
Fetch
https://postback.trafficmotor.com/sn/
684.98800002271
847.39800001262
389
0
200
text/html
Fetch
https://www.google.com/afs/gen_204?client=dp-namemedia01&output=uds_ads_only&zx=d1s7crls87cs&aqid=8eG6XuDgNovtogbryY7gDA&psid=3767353295&pbt=bo&adbn=master-1&uio=bottom|18|10|10|||https%3A%2F%2Fafs.googleusercontent.com%2Fdp-namemedia%2Fbullet-arrows-orange.png|18||||2|||||%23525252|||%23b4b4b4|transparent||||||%23e08d20|1||||||||16||||24||||||40|||||true||||||%235595e9|||true|true|false|2||relatedLinks|false|relatedsearch|3767353295||412|
705.00499999616
736.00000003353
572
0
204
text/html
Image
https://www.google.com/js/bg/hoakTGSdv_jI8DI7b71Hu182_w1HnQYnfKWqXl6Cy2E.js
708.19899998605
711.679
6104
12464
200
text/javascript
Script
https://api.aws.parking.godaddy.com/v1/parkingEvents
710.14300000388
791.90700000618
157
0
200
text/plain
Fetch
https://api.parking.godaddy.com/v1/parkingEvents
797.20400000224
864.77600003127
166
0
200
text/plain
Fetch
https://postback.trafficmotor.com/sn/
848.83900004206
986.17400001967
231
3
200
application/json
Fetch
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)
94.704
6.422
247.638
5.989
294.212
8.007
370.379
55.617
501.348
27.986
634.852
6.021
669.57
27.79
698.246
6.04
710.316
9.881
731.481
76.428
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Howwasyourday.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Howwasyourday.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Howwasyourday.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Howwasyourday.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Howwasyourday.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Howwasyourday.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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.
Server response times are low (TTFB) — Root document took 70 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Howwasyourday.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Howwasyourday.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 232 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://d1hi41nc56pmug.cloudfront.net/static/js/main.e38721e2.js
94603
https://www.google.com/adsense/domains/caf.js
60275
https://www.google.com/adsense/domains/caf.js
59949
https://www.google.com/dp/ads?r=m&domain_name=howwasyourday.com&cpp=0&client=dp-namemedia01&channel=00001&adtest=off&adsafe=low&type=3&pcsa=false&psid=3767353295&swp=as-drid-oo-1502969727449347&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300169%2C17300171%2C17300194%2C17300196&format=r6&num=0&output=afd_ads&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1589305841831&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=157&frm=0&uio=st24sa11lt40sl1sr1-&cont=relatedLinks&csize=w412h18&inames=master-1&jsv=27311&rurl=http%3A%2F%2Fwww6.howwasyourday.com%2F%3Fs_token%3D1589305841.5030060368%26uuid%3D1589305841.5030060368&referer=http%3A%2F%2Fhowwasyourday.com%2F
7593
https://www.google.com/js/bg/hoakTGSdv_jI8DI7b71Hu182_w1HnQYnfKWqXl6Cy2E.js
6104
http://howwasyourday.com/
1729
https://api.aws.parking.godaddy.com/v1/domains/www6.howwasyourday.com/landerParams
1551
http://www6.howwasyourday.com/?s_token=1589305841.5030060368&uuid=1589305841.5030060368
1363
https://afs.googleusercontent.com/dp-namemedia/bullet-arrows-orange.png
1121
http://howwasyourday.com/mtm/async/eyJ1cmkiOiIvIiwiYXJncyI6IiIsInJlZmVyZXIiOiIifQ:1jYZ3B:I4jsZzmF8aEYm7N6-0a12V8SRsY/1
733
Avoids an excessive DOM size — 19 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
19
Maximum DOM Depth
7
Maximum Child Elements
4
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Howwasyourday.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.8 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js
509.88
461.704
37.312
Other
373.496
121.816
8.904
https://d1hi41nc56pmug.cloudfront.net/static/js/main.e38721e2.js
218.288
199.168
19.12
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
792.748
Other
174.216
Script Parsing & Compilation
70.464
Style & Layout
45.588
Parse HTML & CSS
18.276
Rendering
15.56
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 19 requests • 232 KB
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
19
237312
Script
4
220931
Document
4
10685
Other
9
4003
Image
2
1693
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
15
233487

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.

Metrics

Time to Interactive — 4.4 s
The time taken for the page to become fully interactive.
First CPU Idle — 4.3 s
The time taken for the page's main thread to be quiet enough to handle input.

Other

Total Blocking Time — 420 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).
First Contentful Paint (3G) — 4238 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Diagnostics

Serve static assets with an efficient cache policy — 2 resources found
Howwasyourday.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
https://d1hi41nc56pmug.cloudfront.net/static/js/main.e38721e2.js
0
94603
https://afs.googleusercontent.com/dp-namemedia/bullet-arrows-orange.png
82800000
1121

Metrics

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

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 260 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Size (Bytes) Main-Thread Blocking Time (Ms)
134493
255.54
2650
0
72

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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-*]` 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.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Howwasyourday.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Howwasyourday.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Howwasyourday.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

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.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Names and labels

Document doesn't have 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.
Failing Elements
`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
85

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
React (Fast path)
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 3 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
http://howwasyourday.com/
http://howwasyourday.com/mtm/async/eyJ1cmkiOiIvIiwiYXJncyI6IiIsInJlZmVyZXIiOiIifQ:1jYZ3B:I4jsZzmF8aEYm7N6-0a12V8SRsY/1
http://www6.howwasyourday.com/?s_token=1589305841.5030060368&uuid=1589305841.5030060368
Uses `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.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 193
73

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of howwasyourday.com on mobile screens.
Document uses legible font sizes — 77.73% 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
dynamic
#copyright
15.64%
11px
dynamic
#privacy
6.64%
11px
Legible text
77.73%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Content Best Practices

Document doesn't have 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.
Failing Elements
Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

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

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

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

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 howwasyourday.com on mobile screens.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 3 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
http://howwasyourday.com/
http://howwasyourday.com/mtm/async/eyJ1cmkiOiIvIiwiYXJncyI6IiIsInJlZmVyZXIiOiIifQ:1jYZ3B:I4jsZzmF8aEYm7N6-0a12V8SRsY/1
http://www6.howwasyourday.com/?s_token=1589305841.5030060368&uuid=1589305841.5030060368
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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 fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.

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: 45.33.23.183
Continent: North America
Country: United States
United States Flag
Region: Texas
City: Dallas
Longitude: -96.8217
Latitude: 32.7787
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Linode
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
doMEn 64.96.209.15
Security

Visitor Safety

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

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
howwasyourday.com. 198.58.118.167 IN 299
howwasyourday.com. 45.33.23.183 IN 299
howwasyourday.com. 45.33.2.79 IN 299
howwasyourday.com. 45.56.79.23 IN 299
howwasyourday.com. 45.79.19.196 IN 299
howwasyourday.com. 96.126.123.244 IN 299

NS Records

Host Nameserver Class TTL
howwasyourday.com. ns1.uniregistrymarket.link. IN 299
howwasyourday.com. ns2.uniregistrymarket.link. IN 299

MX Records

Priority Host Server Class TTL
1 howwasyourday.com. mx247.in-mx.com. IN 299
1 howwasyourday.com. mx247.in-mx.net. IN 299

SOA Records

Domain Name Primary NS Responsible Email TTL
howwasyourday.com. ns1.uniregistrymarket.link. hostmaster.uniregistry.com. 299

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: openresty/1.13.6.1
Date: 12th May, 2020
Content-Type: application/octet-stream
Content-Length: 0
Connection: close

Whois Lookup

Created: 4th October, 2002
Changed: 18th January, 2019
Expires: 4th October, 2020
Registrar: Uniregistrar Corp
Status: clientTransferProhibited
Nameservers: ns1.uniregistrymarket.link
ns2.uniregistrymarket.link
Full Whois: Domain Name: HOWWASYOURDAY.COM
Registry Domain ID: 90928042_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.uniregistrar.com
Registrar URL: http://www.uniregistrar.com
Updated Date: 2019-01-18T03:41:51Z
Creation Date: 2002-10-04T22:37:09Z
Registry Expiry Date: 2020-10-04T22:37:09Z
Registrar: Uniregistrar Corp
Registrar IANA ID: 1659
Registrar Abuse Contact Email: abuse@uniregistry.com
Registrar Abuse Contact Phone: +1.4426008800
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.UNIREGISTRYMARKET.LINK
Name Server: NS2.UNIREGISTRYMARKET.LINK
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2020-05-12T17:50:10Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

Nameservers

Name IP Address
ns1.uniregistrymarket.link 97.74.99.64
ns2.uniregistrymarket.link 173.201.67.64
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
$1,023 USD 2/5