angusnicneven.com

angusnicneven.com is SSL secured

Free website and domain report on angusnicneven.com

Last Updated: 28th April, 2021 Update Now
Overview

Snoop Summary for angusnicneven.com

This is a free and comprehensive report about angusnicneven.com. The domain angusnicneven.com is currently hosted on a server located in United States with the IP address 162.241.24.188, where USD is the local currency and the local language is English. Our records indicate that angusnicneven.com is privately registered by WhoisGuard, Inc.. Angusnicneven.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If angusnicneven.com was to be sold it would possibly be worth $826 USD (based on the daily revenue potential of the website over a 24 month period). Angusnicneven.com is somewhat popular with an estimated 392 daily unique visitors. This report was last updated 28th April, 2021.

About angusnicneven.com

Site Preview: angusnicneven.com angusnicneven.com
Title: Terminal 00
Description: A Terminal revived by Angus Nicneven, the first Arcent. Author of the novel, Stars Bleed.
Keywords and Tags: personal pages
Related Terms: apm terminal elizabeth nj, cathay pacific jfk terminal, terminal, terminal 5, terminal commands, terminal de omnibus retiro, terminal five, terminal server, terminal services client, tickmill mt4 client terminal
Fav Icon:
Age: Over 9 years old
Domain Created: 14th November, 2014
Domain Updated: 16th September, 2019
Domain Expires: 14th November, 2028
Review

Snoop Score

1/5

Valuation

$826 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,999,999
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: 392
Monthly Visitors: 11,931
Yearly Visitors: 143,080
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $34 USD
Yearly Revenue: $408 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: angusnicneven.com 17
Domain Name: angusnicneven 13
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 75
Performance 100
Accessibility 72
Best Practices 87
SEO 73
Progressive Web App 45
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://angusnicneven.com/
Updated: 28th April, 2021

0.60 seconds
First Contentful Paint (FCP)
87%
12%
1%

0.01 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on desktop
100

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.4 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.026
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.4 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 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 angusnicneven.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 Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://angusnicneven.com/
http/1.1
0
237.05499991775
343
0
301
text/html
https://angusnicneven.com/
h2
237.5090001151
419.93100009859
3894
13568
200
text/html
Document
https://angusnicneven.com/terminal00.css
h2
435.88200001977
503.01699992269
801
1030
200
text/css
Stylesheet
https://angusnicneven.com/style.css
h2
436.14300014451
646.27999998629
555
208
200
text/css
Stylesheet
https://angusnicneven.com/main.js
h2
436.34500005282
643.54300010018
1214
1747
200
application/javascript
Script
https://angusnicneven.com/images/00warning.gif
h2
645.86300007068
839.17000005022
400805
400454
200
image/gif
Image
https://angusnicneven.com/images/deadend.gif
h2
648.23099994101
822.82300014049
141592
141241
200
image/gif
Image
https://angusnicneven.com/images/back1.gif
h2
650.95299994573
873.98599996231
44131
43781
200
image/gif
Image
https://angusnicneven.com/images/back2.gif
h2
651.2760000769
791.66500014253
43909
43559
200
image/gif
Image
https://angusnicneven.com/images/bbn.gif
h2
651.43700013869
821.18199998513
6948
6599
200
image/gif
Image
https://angusnicneven.com/images/zz.gif
h2
651.69500000775
857.04399994574
2800
2451
200
image/gif
Image
https://angusnicneven.com/images/zz3.png
h2
651.99499996379
871.21100001968
489
141
200
image/png
Image
https://angusnicneven.com/images/zz2.gif
h2
652.42399997078
837.26399997249
2015
1666
200
image/gif
Image
https://angusnicneven.com/images/zz4.gif
h2
652.86000003107
861.22999992222
2905
2556
200
image/gif
Image
https://angusnicneven.com/images/Oneiromancy.png
h2
653.16700004041
862.63000010513
36664
36314
200
image/png
Image
https://angusnicneven.com/images/beyondthepointof.gif
h2
653.33899995312
821.51299994439
22126
21776
200
image/gif
Image
https://angusnicneven.com/images/thisshouldnotexist.gif
h2
653.58799998648
872.06700001843
241254
240903
200
image/gif
Image
https://www.google-analytics.com/analytics.js
h2
653.7880001124
660.45700013638
20199
49153
200
text/javascript
Script
https://angusnicneven.com/images/ListenWell.gif
h2
664.76999991573
956.20499993674
393465
393114
200
image/gif
Image
https://angusnicneven.com/cursor/rrw.png
h2
665.66199995577
836.78400004283
571
223
200
image/png
Image
https://angusnicneven.com/images/00havemercy.gif
h2
665.86000006646
1053.5339999478
1415137
1414785
200
image/gif
Image
https://angusnicneven.com/cursor/rrw2.png
h2
670.83099996671
820.39800006896
581
233
200
image/png
Image
https://angusnicneven.com/images/un.gif
h2
670.98900000565
820.88200002909
2825
2476
200
image/gif
Image
https://angusnicneven.com/images/rre2.gif
h2
671.13899998367
948.95400013775
999180
998829
200
image/gif
Image
https://angusnicneven.com/music/terminalwaves.mp3
h2
725.92499991879
954.93799983524
476
65536
206
audio/mpeg
Media
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=1886063969&t=pageview&_s=1&dl=https%3A%2F%2Fangusnicneven.com%2F&ul=en-us&de=UTF-8&dt=Terminal%2000&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=514415307&gjid=654382227&cid=1097890441.1619629783&tid=UA-79198042-1&_gid=27912180.1619629783&_r=1&_slc=1&z=1733075619
h2
764.82799998485
771.18999999948
621
2
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
464.9
9.601
689.559
25.733
715.305
37.859
753.583
13.202
772.157
34.432
915.322
16.614
934.016
14.798
949.19
16.424
965.778
16.34
982.622
16.666
1001.342
14.014
1019.308
12.928
1035.222
13.651
1050.246
15.262
1066.12
15.916
1083.397
15.241
1099.373
16.098
1116.162
15.883
1133.357
15.544
1149.795
15.762
1166.369
16.169
1183.547
15.369
1199.992
15.763
1219.272
14.127
1233.52
16.887
1251.185
14.687
1266.041
15.992
1282.834
15.841
1299.732
15.94
1315.944
16.222
1332.846
16.145
1349.681
16.026
1366.016
15.919
1382.467
16.158
1399.182
16.23
1416.258
15.907
1432.88
15.802
1449.142
16.146
1465.641
16.245
1482.63
16.005
1499.231
16.123
1515.895
16.269
1532.871
15.814
1549.62
15.87
1565.755
16.018
1582.397
16.305
1599.318
15.944
1615.789
16.41
1632.87
15.904
1649.353
16.046
1665.867
16.232
1682.737
15.905
1699.248
16.114
1716.016
16.242
1733.08
15.661
1749.368
15.89
1765.596
16.363
1782.673
16.191
1799.436
16.055
1815.909
16.323
1833.099
16.154
1849.944
15.286
1865.517
16.376
1882.535
16.262
1899.441
15.902
1915.949
16.118
1932.731
15.969
1949.158
16.233
1965.789
16.07
1982.576
16.216
1999.498
15.825
2015.844
17.066
2033.334
15.547
2049.86
15.695
2065.94
16.789
2083.498
15.357
2099.49
16.911
2116.994
15.191
2132.825
16.069
2149.78
16.049
2165.994
16.23
2183.608
15.583
2199.84
15.886
2216.246
18.652
2234.922
5.224
2240.204
8.655
2249.403
15.975
2265.713
16.577
2283.23
15.563
2299.337
16.885
2316.932
15.269
2333.01
19.804
2353.542
12.116
2366.209
16.566
2383.52
15.804
2399.79
15.641
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. Angusnicneven.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. Angusnicneven.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Angusnicneven.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Angusnicneven.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Angusnicneven.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Angusnicneven.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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.
Initial server response time was short — Root document took 180 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://angusnicneven.com/
183.419
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Angusnicneven.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://angusnicneven.com/
190
https://angusnicneven.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Angusnicneven.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids an excessive DOM size — 203 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
203
Maximum DOM Depth
are
6
Maximum Child Elements
89
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. Angusnicneven.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.0 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://angusnicneven.com/
1530.473
4.413
1.234
Unattributable
70.121
1.424
0.315
Minimizes main-thread work — 1.6 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)
Rendering
1361.273
Other
128.438
Style & Layout
93.413
Script Evaluation
40.35
Parse HTML & CSS
16.777
Script Parsing & Compilation
3.509
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 — 26 requests • 3,697 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
3785500
Image
18
3757397
Script
2
21413
Document
1
3894
Stylesheet
2
1356
Other
2
964
Media
1
476
Font
0
0
Third-party
2
20820
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
20820
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

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.

Diagnostics

Avoid enormous network payloads — Total size was 3,696 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://angusnicneven.com/images/00havemercy.gif
1415137
https://angusnicneven.com/images/rre2.gif
999180
https://angusnicneven.com/images/00warning.gif
400805
https://angusnicneven.com/images/ListenWell.gif
393465
https://angusnicneven.com/images/thisshouldnotexist.gif
241254
https://angusnicneven.com/images/deadend.gif
141592
https://angusnicneven.com/images/back1.gif
44131
https://angusnicneven.com/images/back2.gif
43909
https://angusnicneven.com/images/Oneiromancy.png
36664
https://angusnicneven.com/images/beyondthepointof.gif
22126

Opportunities

Use video formats for animated content — Potential savings of 2,479 KiB
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.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://angusnicneven.com/images/00havemercy.gif
1414785
1103532
https://angusnicneven.com/images/rre2.gif
998829
739133
https://angusnicneven.com/images/00warning.gif
400454
248281
https://angusnicneven.com/images/ListenWell.gif
393114
243731
https://angusnicneven.com/images/thisshouldnotexist.gif
240903
134906
https://angusnicneven.com/images/deadend.gif
141241
69208

Diagnostics

Serve static assets with an efficient cache policy — 23 resources found
Angusnicneven.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20199
https://angusnicneven.com/images/00havemercy.gif
604800000
1415137
https://angusnicneven.com/images/rre2.gif
604800000
999180
https://angusnicneven.com/images/00warning.gif
604800000
400805
https://angusnicneven.com/images/ListenWell.gif
604800000
393465
https://angusnicneven.com/images/thisshouldnotexist.gif
604800000
241254
https://angusnicneven.com/images/deadend.gif
604800000
141592
https://angusnicneven.com/images/back1.gif
604800000
44131
https://angusnicneven.com/images/back2.gif
604800000
43909
https://angusnicneven.com/images/Oneiromancy.png
604800000
36664
https://angusnicneven.com/images/beyondthepointof.gif
604800000
22126
https://angusnicneven.com/images/bbn.gif
604800000
6948
https://angusnicneven.com/images/zz4.gif
604800000
2905
https://angusnicneven.com/images/un.gif
604800000
2825
https://angusnicneven.com/images/zz.gif
604800000
2800
https://angusnicneven.com/images/zz2.gif
604800000
2015
https://angusnicneven.com/main.js
604800000
1214
https://angusnicneven.com/terminal00.css
604800000
801
https://angusnicneven.com/cursor/rrw2.png
604800000
581
https://angusnicneven.com/cursor/rrw.png
604800000
571
https://angusnicneven.com/style.css
604800000
555
https://angusnicneven.com/images/zz3.png
604800000
489
https://angusnicneven.com/music/terminalwaves.mp3
604800000
476
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
https://angusnicneven.com/images/ListenWell.gif
img
https://angusnicneven.com/images/thisshouldnotexist.gif
https://angusnicneven.com/images/Oneiromancy.png
https://angusnicneven.com/images/beyondthepointof.gif
https://angusnicneven.com/images/bbn.gif
https://angusnicneven.com/images/bbn.gif
https://angusnicneven.com/images/zz4.gif
https://angusnicneven.com/images/zz4.gif
https://angusnicneven.com/images/zz.gif
https://angusnicneven.com/images/zz.gif
https://angusnicneven.com/images/zz.gif
https://angusnicneven.com/images/zz.gif
say
https://angusnicneven.com/images/zz2.gif
https://angusnicneven.com/images/zz2.gif
https://angusnicneven.com/images/zz2.gif
are
https://angusnicneven.com/images/zz2.gif
or
https://angusnicneven.com/images/zz3.png
to
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
of
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
you
https://angusnicneven.com/images/zz3.png
see
https://angusnicneven.com/images/zz3.png
are
https://angusnicneven.com/images/zz3.png
so
https://angusnicneven.com/images/zz3.png
but
https://angusnicneven.com/images/zz3.png
you
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
to
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
so
https://angusnicneven.com/images/zz3.png
72

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a `[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"]`
Angusnicneven.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

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

Audits

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.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://angusnicneven.com/
Allowed

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for angusnicneven.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.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
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 angusnicneven.com on mobile screens.

Crawling and Indexing

Links are not 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

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Manual Checks

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

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

Installable

Web app manifest and service worker 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.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of angusnicneven.com on mobile screens.
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) 65
Performance 70
Accessibility 72
Best Practices 80
SEO 62
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://angusnicneven.com/
Updated: 28th April, 2021

1.33 seconds
First Contentful Paint (FCP)
67%
28%
5%

0.02 seconds
First Input Delay (FID)
97%
3%
0%

Simulate loading on mobile
70

Performance

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

Metrics

First Contentful Paint — 1.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.043
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 3.4 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 1.4 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://angusnicneven.com/
http/1.1
0
103.16699999385
343
0
301
text/html
https://angusnicneven.com/
h2
103.98799995892
236.38000001665
3894
13568
200
text/html
Document
https://angusnicneven.com/terminal00.css
h2
254.12499997765
418.14299998805
801
1030
200
text/css
Stylesheet
https://angusnicneven.com/style.css
h2
254.38499997836
304.57400006708
555
208
200
text/css
Stylesheet
https://angusnicneven.com/main.js
h2
254.70499997027
304.00800006464
1214
1747
200
application/javascript
Script
https://angusnicneven.com/images/00warning.gif
h2
330.22500004154
537.11699997075
400805
400454
200
image/gif
Image
https://angusnicneven.com/images/deadend.gif
h2
421.81700002402
606.45299998578
141592
141241
200
image/gif
Image
https://angusnicneven.com/images/back1.gif
h2
423.70499996468
535.97399999853
44131
43781
200
image/gif
Image
https://angusnicneven.com/images/back2.gif
h2
423.84199996013
641.27999998163
43909
43559
200
image/gif
Image
https://angusnicneven.com/images/bbn.gif
h2
425.81699998118
534.03600002639
6948
6599
200
image/gif
Image
https://angusnicneven.com/images/zz.gif
h2
427.96000000089
608.04500000086
2800
2451
200
image/gif
Image
https://angusnicneven.com/images/zz3.png
h2
428.13799995929
642.45200005826
489
141
200
image/png
Image
https://angusnicneven.com/images/zz2.gif
h2
428.28300001565
536.50699998252
2015
1666
200
image/gif
Image
https://angusnicneven.com/images/zz4.gif
h2
428.43099997845
605.76700000092
2905
2556
200
image/gif
Image
https://angusnicneven.com/images/Oneiromancy.png
h2
428.57900005765
639.43900004961
36664
36314
200
image/png
Image
https://angusnicneven.com/images/beyondthepointof.gif
h2
428.81700000726
645.68199997302
22126
21776
200
image/gif
Image
https://angusnicneven.com/images/thisshouldnotexist.gif
h2
430.83800002933
597.66900003888
241254
240903
200
image/gif
Image
https://www.google-analytics.com/analytics.js
h2
431.081000017
439.28599997889
20199
49153
200
text/javascript
Script
https://angusnicneven.com/images/ListenWell.gif
h2
452.06000003964
734.88100001123
393465
393114
200
image/gif
Image
https://angusnicneven.com/cursor/rrw.png
h2
453.24100006837
709.23499995843
571
223
200
image/png
Image
https://angusnicneven.com/images/00havemercy.gif
h2
453.42599996366
817.27600004524
1415137
1414785
200
image/gif
Image
https://angusnicneven.com/cursor/rrw2.png
h2
460.93900001142
632.92300002649
581
233
200
image/png
Image
https://angusnicneven.com/images/un.gif
h2
461.12100000028
640.50099998713
2825
2476
200
image/gif
Image
https://angusnicneven.com/images/rre2.gif
h2
461.88499999698
835.73399996385
999180
998829
200
image/gif
Image
https://angusnicneven.com/music/terminalwaves.mp3
h2
646.58199995756
832.88299990818
476
65536
206
audio/mpeg
Media
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=2051346259&t=pageview&_s=1&dl=https%3A%2F%2Fangusnicneven.com%2F&ul=en-us&de=UTF-8&dt=Terminal%2000&sd=24-bit&sr=360x640&vp=980x1742&je=0&_u=IEBAAEABAAAAAC~&jid=1639713429&gjid=1533535361&cid=63097377.1619629800&tid=UA-79198042-1&_gid=1347773644.1619629800&_r=1&_slc=1&z=966555701
h2
845.30599997379
850.86899995804
621
2
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
313.164
9.989
330.357
42.528
493.079
44.487
537.583
143.397
682.417
35.881
725.088
57.239
782.609
11.009
797.485
5.965
809.958
6.146
816.299
102.289
933.421
37.207
971.015
5.38
977.204
19.555
999.254
14.265
1079.473
26.34
1106.133
9.272
1132.751
70.377
1203.169
5.411
1217.031
15.866
1233.059
42.657
1275.917
6.993
1283.27
17.804
1301.333
16.458
1317.833
15.129
1370.959
24.314
1395.334
12.729
1408.433
8.103
1416.579
53.755
1480.834
14.376
1499.438
17.128
1516.652
16.262
1533.135
40.985
1574.382
13.679
1588.104
13.33
1601.637
14.789
1616.635
16.357
1633.284
40.529
1682.831
16.969
1699.948
16.489
1716.703
58.072
1775.021
8.053
1783.444
16.243
1800.257
15.982
1816.401
16.672
1833.318
39.453
1882.678
18.007
1900.895
18.772
1919.711
74.335
1994.25
17.598
2032.552
16.836
2049.537
35.168
2092.255
15.824
2115.797
17.224
2133.069
16.238
2149.472
20.663
2177.892
15.634
2193.562
15.516
2209.31
7.364
2216.87
16.235
2233.439
53.476
2286.994
13.557
2332.601
38.052
2370.856
19.145
2401.302
15.227
2416.693
16.422
2433.359
16.021
2472.535
7.95
2485.348
15.173
2500.574
19.335
2519.957
12.927
2533.011
43.898
2576.963
10.325
2649.041
32.051
2772.948
32.492
2805.517
5.871
2832.368
16.868
2849.359
16.586
2866.052
18.078
2885.938
26.375
2912.361
8.357
3065.672
8.232
3090.607
7.419
3170.199
8.489
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 2638 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Properly size images
Images can slow down the page's load time. Angusnicneven.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Angusnicneven.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Angusnicneven.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Angusnicneven.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Angusnicneven.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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.
Initial server response time was short — Root document took 130 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://angusnicneven.com/
133.388
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Angusnicneven.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://angusnicneven.com/
630
https://angusnicneven.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Angusnicneven.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids an excessive DOM size — 203 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
203
Maximum DOM Depth
are
6
Maximum Child Elements
89
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. Angusnicneven.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.4 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://angusnicneven.com/
7470.012
22.716
5.964
Unattributable
773.02
10.232
0.92
https://www.google-analytics.com/analytics.js
415.38
393.816
9.568
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 — 26 requests • 3,697 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
3785500
Image
18
3757397
Script
2
21413
Document
1
3894
Stylesheet
2
1356
Other
2
964
Media
1
476
Font
0
0
Third-party
2
20820
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
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 — 20 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://angusnicneven.com/
800
287
https://www.google-analytics.com/analytics.js
2422
205
https://angusnicneven.com/main.js
1292
178
Unattributable
630
170
Unattributable
1584
149
https://angusnicneven.com/
3407
149
Unattributable
1148
144
https://angusnicneven.com/
1854
141
https://angusnicneven.com/
3041
116
https://angusnicneven.com/
1470
114
https://angusnicneven.com/
2285
108
https://angusnicneven.com/
3928
107
https://angusnicneven.com/
4366
88
https://angusnicneven.com/
2027
85
https://angusnicneven.com/
2694
82
https://angusnicneven.com/
2893
81
https://angusnicneven.com/
3254
79
https://angusnicneven.com/
4062
76
https://angusnicneven.com/
3625
70
https://angusnicneven.com/
4539
65

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Largest Contentful Paint — 3.7 s
The timing of the largest text or image that is painted.
Time to Interactive — 4.1 s
The time taken for the page to become fully interactive.

Other

Max Potential First Input Delay — 210 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 80 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 angusnicneven.com as laggy when the latency is higher than 0.05 seconds.

Opportunities

Eliminate render-blocking resources — Potential savings of 310 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Angusnicneven.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://angusnicneven.com/terminal00.css
801
150

Diagnostics

Avoid enormous network payloads — Total size was 3,696 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://angusnicneven.com/images/00havemercy.gif
1415137
https://angusnicneven.com/images/rre2.gif
999180
https://angusnicneven.com/images/00warning.gif
400805
https://angusnicneven.com/images/ListenWell.gif
393465
https://angusnicneven.com/images/thisshouldnotexist.gif
241254
https://angusnicneven.com/images/deadend.gif
141592
https://angusnicneven.com/images/back1.gif
44131
https://angusnicneven.com/images/back2.gif
43909
https://angusnicneven.com/images/Oneiromancy.png
36664
https://angusnicneven.com/images/beyondthepointof.gif
22126

Metrics

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

Use video formats for animated content — Potential savings of 2,479 KiB
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.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://angusnicneven.com/images/00havemercy.gif
1414785
1103532
https://angusnicneven.com/images/rre2.gif
998829
739133
https://angusnicneven.com/images/00warning.gif
400454
248281
https://angusnicneven.com/images/ListenWell.gif
393114
243731
https://angusnicneven.com/images/thisshouldnotexist.gif
240903
134906
https://angusnicneven.com/images/deadend.gif
141241
69208

Diagnostics

Serve static assets with an efficient cache policy — 23 resources found
Angusnicneven.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20199
https://angusnicneven.com/images/00havemercy.gif
604800000
1415137
https://angusnicneven.com/images/rre2.gif
604800000
999180
https://angusnicneven.com/images/00warning.gif
604800000
400805
https://angusnicneven.com/images/ListenWell.gif
604800000
393465
https://angusnicneven.com/images/thisshouldnotexist.gif
604800000
241254
https://angusnicneven.com/images/deadend.gif
604800000
141592
https://angusnicneven.com/images/back1.gif
604800000
44131
https://angusnicneven.com/images/back2.gif
604800000
43909
https://angusnicneven.com/images/Oneiromancy.png
604800000
36664
https://angusnicneven.com/images/beyondthepointof.gif
604800000
22126
https://angusnicneven.com/images/bbn.gif
604800000
6948
https://angusnicneven.com/images/zz4.gif
604800000
2905
https://angusnicneven.com/images/un.gif
604800000
2825
https://angusnicneven.com/images/zz.gif
604800000
2800
https://angusnicneven.com/images/zz2.gif
604800000
2015
https://angusnicneven.com/main.js
604800000
1214
https://angusnicneven.com/terminal00.css
604800000
801
https://angusnicneven.com/cursor/rrw2.png
604800000
581
https://angusnicneven.com/cursor/rrw.png
604800000
571
https://angusnicneven.com/style.css
604800000
555
https://angusnicneven.com/images/zz3.png
604800000
489
https://angusnicneven.com/music/terminalwaves.mp3
604800000
476
Minimize main-thread work — 8.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Rendering
5438.672
Other
1400.368
Style & Layout
1266.376
Script Evaluation
433.888
Parse HTML & CSS
127.304
Script Parsing & Compilation
17.86
Reduce the impact of third-party code — Third-party code blocked the main thread for 340 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
20820
339.872
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
https://angusnicneven.com/images/ListenWell.gif
img
https://angusnicneven.com/images/thisshouldnotexist.gif
https://angusnicneven.com/images/Oneiromancy.png
https://angusnicneven.com/images/beyondthepointof.gif
https://angusnicneven.com/images/bbn.gif
https://angusnicneven.com/images/bbn.gif
https://angusnicneven.com/images/zz4.gif
https://angusnicneven.com/images/zz4.gif
https://angusnicneven.com/images/zz.gif
https://angusnicneven.com/images/zz.gif
https://angusnicneven.com/images/zz.gif
https://angusnicneven.com/images/zz.gif
say
https://angusnicneven.com/images/zz2.gif
https://angusnicneven.com/images/zz2.gif
https://angusnicneven.com/images/zz2.gif
are
https://angusnicneven.com/images/zz2.gif
or
https://angusnicneven.com/images/zz3.png
to
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
of
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
you
https://angusnicneven.com/images/zz3.png
see
https://angusnicneven.com/images/zz3.png
are
https://angusnicneven.com/images/zz3.png
so
https://angusnicneven.com/images/zz3.png
but
https://angusnicneven.com/images/zz3.png
you
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
to
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
https://angusnicneven.com/images/zz3.png
so
https://angusnicneven.com/images/zz3.png
72

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a `[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"]`
Angusnicneven.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

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

Audits

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.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://angusnicneven.com/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://angusnicneven.com/images/Oneiromancy.png
451 x 451
451 x 451
902 x 902
https://angusnicneven.com/images/ListenWell.gif
450 x 450
450 x 450
900 x 900
https://angusnicneven.com/images/00warning.gif
250 x 250
250 x 250
500 x 500
https://angusnicneven.com/images/bbn.gif
175 x 35
175 x 35
350 x 70
https://angusnicneven.com/images/zz4.gif
45 x 45
45 x 45
90 x 90
https://angusnicneven.com/images/zz.gif
35 x 35
35 x 35
70 x 70
https://angusnicneven.com/images/zz2.gif
35 x 35
35 x 35
70 x 70
https://angusnicneven.com/images/zz3.png
35 x 35
35 x 35
70 x 70

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for angusnicneven.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.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
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

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 angusnicneven.com on mobile screens.
Document doesn't use legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are not sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Crawling and Indexing

Links are not 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

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Manual Checks

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

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

Installable

Web app manifest and service worker 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.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of angusnicneven.com on mobile screens.
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: 162.241.24.188
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
Unified Layer
Registration

Domain Registrant

Private Registration: Yes
Name: WhoisGuard Protected
Organization: WhoisGuard, Inc.
Country: PA
City: Panama
State: Panama
Post Code: 00000
Email: 50e1eb43ce184b2fa0b6bc5f64767b87.protect@whoisguard.com
Phone: +507.8365503
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NAMECHEAP INC 104.16.100.56
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: webdisk.angusnicneven.com
Issued By: R3
Valid From: 16th April, 2021
Valid To: 15th July, 2021
Subject: CN = webdisk.angusnicneven.com
Hash: 6bdc2df9
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x0339F4EFB280C10CB58C3A29E9FA427455C2
Serial Number (Hex): 0339F4EFB280C10CB58C3A29E9FA427455C2
Valid From: 16th April, 2024
Valid To: 15th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Apr 16 15:29:37.375 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:11:1E:81:A0:55:5E:09:5D:7A:AD:F4:92:
CC:EF:B9:B0:DC:8F:02:E1:54:38:8C:89:93:4D:FF:04:
88:13:0B:F4:02:20:6A:1E:85:37:06:2F:16:47:E9:BF:
47:E4:03:A5:63:46:14:F9:84:EC:1B:CC:C2:D9:B8:AC:
D2:82:B7:59:D5:D4
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Apr 16 15:29:37.394 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C6:D2:70:0E:86:1C:56:18:8F:8B:5B:
65:E8:13:7A:49:96:E9:63:AB:E7:BC:53:89:51:05:95:
59:3A:C1:C9:C0:02:21:00:EF:8D:F0:03:B0:02:74:D1:
39:4A:7E:21:7F:6F:A0:CA:3B:DF:73:CB:AE:0F:1B:8B:
3C:00:06:2D:FB:EF:22:8E
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:autodiscover.angusnicneven.com
DNS:cpanel.angusnicneven.com
DNS:cpcalendars.angusnicneven.com
DNS:cpcontacts.angusnicneven.com
DNS:mail.angusnicneven.com
DNS:webdisk.angusnicneven.com
DNS:webmail.angusnicneven.com
DNS:www.angusnicneven.com
DNS:angusnicneven.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 28th April, 2021
Server: Apache
Content-Type: text/html; charset=utf-8
Content-Security-Policy: upgrade-insecure-requests;
Upgrade: h2,h2c
Connection: Upgrade
Last-Modified: 14th April, 2020
Accept-Ranges: bytes
Content-Length: 13568
Vary: Accept-Encoding
host-header: c2hhcmVkLmJsdWVob3N0LmNvbQ==

Whois Lookup

Created: 14th November, 2014
Changed: 16th September, 2019
Expires: 14th November, 2028
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
Nameservers: ns1.bluehost.com
ns2.bluehost.com
Owner Name: Withheld for Privacy Purposes
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: Kalkofnsvegur 2
Owner Post Code: 101
Owner City: Reykjavik
Owner State: Capital Region
Owner Country: IS
Owner Phone: +354.4212434
Owner Email: aec39e6103a142a9b50f3996c6819887.protect@withheldforprivacy.com
Admin Name: Withheld for Privacy Purposes
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin Post Code: 101
Admin City: Reykjavik
Admin State: Capital Region
Admin Country: IS
Admin Phone: +354.4212434
Admin Email: aec39e6103a142a9b50f3996c6819887.protect@withheldforprivacy.com
Tech Name: Withheld for Privacy Purposes
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech Post Code: 101
Tech City: Reykjavik
Tech State: Capital Region
Tech Country: IS
Tech Phone: +354.4212434
Tech Email: aec39e6103a142a9b50f3996c6819887.protect@withheldforprivacy.com
Full Whois: Domain name: angusnicneven.com
Registry Domain ID: 1885370626_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2019-09-16T03:16:00.71Z
Creation Date: 2014-11-14T19:57:34.00Z
Registrar Registration Expiration Date: 2028-11-14T19:57:34.00Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Withheld for Privacy Purposes
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: Kalkofnsvegur 2
Registrant City: Reykjavik
Registrant State/Province: Capital Region
Registrant Postal Code: 101
Registrant Country: IS
Registrant Phone: +354.4212434
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: aec39e6103a142a9b50f3996c6819887.protect@withheldforprivacy.com
Registry Admin ID:
Admin Name: Withheld for Privacy Purposes
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin City: Reykjavik
Admin State/Province: Capital Region
Admin Postal Code: 101
Admin Country: IS
Admin Phone: +354.4212434
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: aec39e6103a142a9b50f3996c6819887.protect@withheldforprivacy.com
Registry Tech ID:
Tech Name: Withheld for Privacy Purposes
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech City: Reykjavik
Tech State/Province: Capital Region
Tech Postal Code: 101
Tech Country: IS
Tech Phone: +354.4212434
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: aec39e6103a142a9b50f3996c6819887.protect@withheldforprivacy.com
Name Server: ns1.bluehost.com
Name Server: ns2.bluehost.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-04-27T21:09:39.05Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

Nameservers

Name IP Address
ns1.bluehost.com 162.159.24.80
ns2.bluehost.com 162.159.25.175
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5
$975 USD 1/5
0/5