Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

nifty.org

nifty.org is SSL secured

Free website and domain report on nifty.org

Last Updated: 26th April, 2021 Update Now
Overview

Snoop Summary for nifty.org

This is a free and comprehensive report about nifty.org. Nifty.org is hosted in Cedar Knolls, New Jersey in United States on a server with an IP address of 172.104.9.50, where USD is the local currency and the local language is English. Our records indicate that nifty.org is owned/operated by Statutory Masking Enabled. Nifty.org is expected to earn an estimated $111 USD per day from advertising revenue. The sale of nifty.org would possibly be worth $80,732 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Nifty.org receives an estimated 26,148 unique visitors every day - a massive amount of traffic! This report was last updated 26th April, 2021.

About nifty.org

Site Preview:
Title: Nifty Archive
Description: A freely-accessible archive of tens of thousands of sexually-explicit erotica stories
Keywords and Tags: adult content, popular, pornography, spoken only, text
Related Terms: geocities archive, nifty future, nifty future tips, nifty jackpot, nifty options, nifty options providers, niftytrader sgx nifty, sexually deprived memes, sorabji archive, v archive
Fav Icon:
Age: Over 27 years old
Domain Created: 21st May, 1997
Domain Updated: 23rd March, 2021
Domain Expires: 22nd May, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$80,732 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 29,957
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: 26,148
Monthly Visitors: 795,866
Yearly Visitors: 9,544,065
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $111 USD
Monthly Revenue: $3,366 USD
Yearly Revenue: $40,361 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: nifty.org 9
Domain Name: nifty 5
Extension (TLD): org 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.50 seconds
Load Time Comparison: Faster than 95% of sites

PageSpeed Insights

Avg. (All Categories) 75
Performance 97
Accessibility 78
Best Practices 80
SEO 83
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.nifty.org/nifty/
Updated: 26th April, 2021

0.94 seconds
First Contentful Paint (FCP)
78%
19%
3%

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

97

Performance

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

Metrics

First Contentful Paint — 0.8 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 — 1.0 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.8 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.033
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.8 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.8 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 nifty.org 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://nifty.org/
http/1.1
0
67.534000001615
265
0
301
text/html
https://nifty.org/
http/1.1
68.049000001338
223.82300000027
265
0
301
text/html
https://www.nifty.org/
h2
224.40099999949
293.00599999988
996
1427
200
text/html
Document
https://www.google-analytics.com/analytics.js
h2
307.81500000012
312.25599999743
20199
49153
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=1246622672&t=pageview&_s=1&dl=https%3A%2F%2Fwww.nifty.org%2F&ul=en-us&de=windows-1252&dt=Nifty%20Erotic%20Stories%20Archive%20Website&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=643646174&gjid=1912884027&cid=727531844.1619464299&tid=UA-76940-1&_gid=153498392.1619464299&_r=1&_slc=1&z=2062291011
h2
341.66600000026
345.68299999955
619
4
200
text/plain
XHR
https://www.nifty.org/nifty/
h2
344.72999999707
419.16599999968
6619
19296
200
text/html
Document
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j90&tid=UA-76940-1&cid=727531844.1619464299&jid=643646174&gjid=1912884027&_gid=153498392.1619464299&_u=IEBAAEAAAAAAAC~&z=1274799423
h2
348.47299999819
352.15800000151
690
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j90&tid=UA-76940-1&cid=727531844.1619464299&jid=643646174&_u=IEBAAEAAAAAAAC~&z=992681733
h2
354.85299999709
361.68799999723
678
42
200
image/gif
Image
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
h2
433.50400000054
465.93800000119
19373
121200
200
text/css
Stylesheet
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
h2
433.72499999532
464.09299999505
3605
23409
200
text/css
Stylesheet
https://www.nifty.org/nifty/styles/disclaimer.css
h2
433.90599999839
487.99899999722
1044
2893
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
h2
434.10399999993
439.01699999697
31013
86659
200
text/javascript
Script
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
h2
434.23199999961
460.55899999919
10766
37045
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-76940-1
h2
467.5470000002
503.1669999953
37289
92536
200
application/javascript
Script
https://www.nifty.org/nifty/images/N_132x86.png
h2
489.3019999945
558.62199999683
6243
5793
200
image/png
Image
https://www.nifty.org/nifty/images/feed-icon-28x28.png
h2
511.21099999727
580.63899999979
2081
1737
200
image/png
Image
https://www.nifty.org/nifty/images/gayback.jpg
h2
517.35799999733
580.06000000023
2453
2108
200
image/jpeg
Image
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/fonts/glyphicons-halflings-regular.woff2
h2
521.45899999596
545.08399999759
19220
18028
200
font/woff2
Font
https://www.googletagmanager.com/gtag/js?id=G-S8YJPTKXR7&l=dataLayer&cx=c
h2
679.22099999851
709.79499999521
46927
120234
200
application/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-S8YJPTKXR7&gtm=2oe4e1&_p=170242446&sr=800x600&ul=en-us&cid=727531844.1619464299&_s=1&dl=https%3A%2F%2Fwww.nifty.org%2Fnifty%2F&dr=https%3A%2F%2Fwww.nifty.org%2F&dt=Nifty%20Erotic%20Stories%20Archive%20-%20Gay%20Fiction&sid=1619464299&sct=1&seg=0&en=page_view&_fv=1&_ss=1
745.15899999824
757.49099999666
0
0
-1
Other
https://www.google-analytics.com/analytics.js
h2
748.54499999492
748.69999999646
20199
49153
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=170242446&t=pageview&_s=1&dl=https%3A%2F%2Fwww.nifty.org%2Fnifty%2F&ul=en-us&de=UTF-8&dt=Nifty%20Erotic%20Stories%20Archive%20-%20Gay%20Fiction&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=AACAAUABAAAAAC~&jid=1821173287&gjid=325173483&cid=727531844.1619464299&tid=UA-76940-1&_gid=153498392.1619464299&_r=1&gtm=2ou4e1&z=175483871
h2
784.338999998
787.77999999875
617
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j90&tid=UA-76940-1&cid=727531844.1619464299&jid=1821173287&gjid=325173483&_gid=153498392.1619464299&_u=AACAAUAAAAAAAC~&z=1080495231
h2
795.60800000036
799.65899999661
690
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j90&tid=UA-76940-1&cid=727531844.1619464299&jid=1821173287&_u=AACAAUAAAAAAAC~&z=1286607935
h2
802.31300000014
810.65699999453
678
42
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
322.859
8.945
345.14
24.156
449.67
8.046
494.373
6.592
516.98
32.771
549.776
72.765
624.38
28.32
657.914
19.659
678.358
9.591
687.99
7.108
697.957
8.981
748.186
32.277
785.237
28.908
981.192
8.72
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Nifty.org should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Nifty.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Nifty.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Nifty.org should consider minifying JS files.
Remove unused CSS — Potential savings of 17 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Nifty.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
19373
17587
Remove unused JavaScript — Potential savings of 21 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-S8YJPTKXR7&l=dataLayer&cx=c
46927
21063
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 80 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.nifty.org/nifty/
75.433
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Nifty.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 227 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-S8YJPTKXR7&l=dataLayer&cx=c
46927
https://www.googletagmanager.com/gtag/js?id=UA-76940-1
37289
https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
31013
https://www.google-analytics.com/analytics.js
20199
https://www.google-analytics.com/analytics.js
20199
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
19373
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/fonts/glyphicons-halflings-regular.woff2
19220
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
10766
https://www.nifty.org/nifty/
6619
https://www.nifty.org/nifty/images/N_132x86.png
6243
Avoids an excessive DOM size — 276 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
276
Maximum DOM Depth
Beginnings
12
Maximum Child Elements
Newest Stories — the Nifty Archive always welcomes new authors and new or revis…
22
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Nifty.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.nifty.org/nifty/
194.621
4.896
2.534
https://www.google-analytics.com/analytics.js
62.147
49.172
6.705
https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
55.78
42.394
1.681
Minimizes main-thread work — 0.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
148.668
Style & Layout
97.975
Other
68.69
Rendering
60.411
Script Parsing & Compilation
17.845
Parse HTML & CSS
12.924
Keep request counts low and transfer sizes small — 24 requests • 227 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
24
232529
Script
6
166393
Stylesheet
3
24022
Font
1
19220
Image
5
12133
Document
2
7615
Other
7
3146
Media
0
0
Third-party
16
212563
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)
SHOW DETAILS
84216
0
SHOW DETAILS
52964
0
SHOW DETAILS
41634
0
SHOW DETAILS
31013
0
SHOW DETAILS
1380
0
SHOW DETAILS
1356
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
Charles, Robert, Brad, Andrew, Laura, Daniel, Brad, Daniel, Arthur, Albert, Ric…
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
New Stories    Publish a Story Announcements Newest Stories — the Nifty Archi…
0.017521508722668
New Stories    Publish a Story Announcements Newest Stories — the Nifty Archi…
0.011714124376448
Archives New Stories Authors Donate Shop
0.003573237712693
New Stories    Publish a Story
2.5079160765624E-5
Publish a Story
1.1564094408883E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations — 4 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element
Archives New Stories Authors Donate Shop
Margie's Gift SF-Fantasy Poetry and Blood Romance Sofie Adult-Friends The Tatto…
A Strange But Happy Friendship Adult-Friends Pegging Peter Relationships Ring i…
Cindy, Laura and I She-Male Jian TV Tingles TV
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

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.

Opportunities

Eliminate render-blocking resources — Potential savings of 340 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Nifty.org 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://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
19373
270
https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
31013
270
Avoid multiple page redirects — Potential savings of 570 ms
Redirects can cause additional delays before the page can begin loading. Nifty.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://nifty.org/
190
https://nifty.org/
150
https://www.nifty.org/
230
https://www.nifty.org/nifty/
0

Diagnostics

Serve static assets with an efficient cache policy — 6 resources found
Nifty.org 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.nifty.org/nifty/images/gayback.jpg
0
2453
https://www.nifty.org/nifty/images/feed-icon-28x28.png
0
2081
https://www.google-analytics.com/analytics.js
7200000
20199
https://www.google-analytics.com/analytics.js
7200000
20199
https://www.nifty.org/nifty/images/N_132x86.png
2592000000
6243
https://www.nifty.org/nifty/styles/disclaimer.css
2592000000
1044

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/fonts/glyphicons-halflings-regular.woff2
23.62500000163
78

Accessibility

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

Tables and lists

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.

Names and labels

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.

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

ARIA

ARIA `progressbar` elements do not 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.
Failing Elements
$3000

Names and labels

Buttons do not 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.
Failing Elements
button
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.

Contrast

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

Tables and lists

`<dl>`'s do not 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.
Failing Elements
Kasey with a K Beginnings Life's Illusions Relationships Miles From Home Colleg…
Margie's Gift SF-Fantasy Poetry and Blood Romance Sofie Adult-Friends The Tatto…
A Strange But Happy Friendship Adult-Friends Pegging Peter Relationships Ring i…
Cindy, Laura and I She-Male Jian TV Tingles TV
Newest Stories — the Nifty Archive always welcomes new authors and new or revis…

Navigation

Heading elements are not 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.
Failing Elements
Established 1992 Over 360,000 stories by over 15,000 authors.

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

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.3.7
jQuery
3.2.1
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://nifty.org/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 8 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
SHOW DETAILS
5
Medium
SHOW DETAILS
3
Medium

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for nifty.org. 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 nifty.org on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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

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

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.
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 nifty.org on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 73
Performance 82
Accessibility 76
Best Practices 80
SEO 83
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.nifty.org/nifty/
Updated: 26th April, 2021

0.84 seconds
First Contentful Paint (FCP)
82%
16%
2%

0.01 seconds
First Input Delay (FID)
98%
1%
1%

82

Performance

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

Metrics

Speed Index — 3.1 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 150 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
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 nifty.org 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://nifty.org/
http/1.1
0
98.687999881804
254
0
301
text/html
https://nifty.org/
http/1.1
99.186999956146
205.85799985565
258
0
301
text/html
https://www.nifty.org/
h2
206.2909998931
249.02999983169
1075
1427
200
text/html
Document
https://www.google-analytics.com/analytics.js
h2
262.70199986175
267.43199978955
20199
49153
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=899364621&t=pageview&_s=1&dl=https%3A%2F%2Fwww.nifty.org%2F&ul=en-us&de=windows-1252&dt=Nifty%20Erotic%20Stories%20Archive%20Website&sd=24-bit&sr=360x640&vp=980x1742&je=0&_u=IEBAAEABAAAAAC~&jid=160830042&gjid=1337587687&cid=583850525.1619464311&tid=UA-76940-1&_gid=297729284.1619464311&_r=1&_slc=1&z=1659305077
h2
289.85399985686
293.68599993177
619
4
200
text/plain
XHR
https://www.nifty.org/nifty/
h2
292.32100001536
311.44599989057
6619
19296
200
text/html
Document
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j90&tid=UA-76940-1&cid=583850525.1619464311&jid=160830042&gjid=1337587687&_gid=297729284.1619464311&_u=IEBAAEAAAAAAAC~&z=1558939957
h2
295.60999991372
299.30399986915
690
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j90&tid=UA-76940-1&cid=583850525.1619464311&jid=160830042&_u=IEBAAEAAAAAAAC~&z=908549706
h2
301.22099979781
307.92999989353
678
42
200
image/gif
Image
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
h2
322.05399987288
362.92300000787
19372
121200
200
text/css
Stylesheet
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
h2
322.18899996951
345.60199989937
3605
23409
200
text/css
Stylesheet
https://www.nifty.org/nifty/styles/disclaimer.css
h2
322.30799994431
340.97699983977
1044
2893
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
h2
322.5809999276
327.6949999854
31013
86659
200
text/javascript
Script
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
h2
322.80500000343
346.91499988548
10741
37045
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-76940-1
h2
349.37099996023
365.66399992444
37289
92536
200
application/javascript
Script
https://www.nifty.org/nifty/images/N_132x86.png
h2
364.49399986304
383.63999989815
6138
5793
200
image/png
Image
https://www.nifty.org/nifty/images/feed-icon-28x28.png
h2
387.18799990602
402.73099998012
2186
1737
200
image/png
Image
https://www.nifty.org/nifty/images/gayback.jpg
h2
393.12399993651
412.43099980056
2453
2108
200
image/jpeg
Image
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/fonts/glyphicons-halflings-regular.woff2
h2
396.25399978831
419.34599983506
19220
18028
200
font/woff2
Font
https://www.googletagmanager.com/gtag/js?id=G-S8YJPTKXR7&l=dataLayer&cx=c
h2
450.36699995399
481.24499991536
46928
120234
200
application/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-S8YJPTKXR7&gtm=2oe4e1&_p=1902010073&sr=360x640&ul=en-us&cid=583850525.1619464311&_s=1&dl=https%3A%2F%2Fwww.nifty.org%2Fnifty%2F&dr=https%3A%2F%2Fwww.nifty.org%2F&dt=Nifty%20Erotic%20Stories%20Archive%20-%20Gay%20Fiction&sid=1619464311&sct=1&seg=0&en=page_view&_fv=1&_ss=1
509.33499983512
517.16199982911
0
0
-1
Other
https://www.google-analytics.com/analytics.js
h2
512.50499999151
512.62900000438
20199
49153
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=1902010073&t=pageview&_s=1&dl=https%3A%2F%2Fwww.nifty.org%2Fnifty%2F&ul=en-us&de=UTF-8&dt=Nifty%20Erotic%20Stories%20Archive%20-%20Gay%20Fiction&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=AACAAUABAAAAAC~&jid=91169922&gjid=834971532&cid=583850525.1619464311&tid=UA-76940-1&_gid=297729284.1619464311&_r=1&gtm=2ou4e1&z=198284576
h2
536.80999996141
539.47899979539
617
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j90&tid=UA-76940-1&cid=583850525.1619464311&jid=91169922&gjid=834971532&_gid=297729284.1619464311&_u=AACAAUAAAAAAAC~&z=958756123
h2
541.78199986927
546.21199984103
690
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j90&tid=UA-76940-1&cid=583850525.1619464311&jid=91169922&_u=AACAAUAAAAAAAC~&z=630614107
h2
548.34400000982
557.22899991088
678
42
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
277.25
7.224
297.973
18.254
339.823
6.064
390.192
5.055
395.863
27.075
422.95
24.15
455.2
5.025
460.246
7.288
469.41
7.52
516.376
26.728
543.599
21.267
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Nifty.org should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Nifty.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Nifty.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Nifty.org should consider minifying JS files.
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 20 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.nifty.org/nifty/
20.123
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Nifty.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 227 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-S8YJPTKXR7&l=dataLayer&cx=c
46928
https://www.googletagmanager.com/gtag/js?id=UA-76940-1
37289
https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
31013
https://www.google-analytics.com/analytics.js
20199
https://www.google-analytics.com/analytics.js
20199
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
19372
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/fonts/glyphicons-halflings-regular.woff2
19220
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
10741
https://www.nifty.org/nifty/
6619
https://www.nifty.org/nifty/images/N_132x86.png
6138
Avoids an excessive DOM size — 276 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
276
Maximum DOM Depth
Beginnings
12
Maximum Child Elements
Newest Stories — the Nifty Archive always welcomes new authors and new or revis…
22
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Nifty.org 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://www.nifty.org/nifty/
230.084
12.08
7.356
https://www.google-analytics.com/analytics.js
184.46
144.188
24.116
https://www.googletagmanager.com/gtag/js?id=G-S8YJPTKXR7&l=dataLayer&cx=c
111.408
97.552
10.056
Unattributable
77.568
3.056
0.512
https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
72.836
61.376
5.836
https://www.googletagmanager.com/gtag/js?id=UA-76940-1
62.356
49.044
10.584
Minimizes main-thread work — 0.8 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
384.732
Other
151.712
Style & Layout
131.28
Script Parsing & Compilation
62.22
Parse HTML & CSS
41.676
Rendering
20.048
Keep request counts low and transfer sizes small — 24 requests • 227 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
24
232565
Script
6
166369
Stylesheet
3
24021
Font
1
19220
Image
5
12133
Document
2
7694
Other
7
3128
Media
0
0
Third-party
16
212538
Minimize third-party usage — Third-party code blocked the main thread for 70 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)
SHOW DETAILS
84217
42.492
SHOW DETAILS
41634
23.728
SHOW DETAILS
52938
0
SHOW DETAILS
31013
0
SHOW DETAILS
1380
0
SHOW DETAILS
1356
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
This website contains sexually-explicit content involving alternative sexualiti…
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
span
8.5371543073911E-6
span
8.5371543073911E-6
span
8.5371543073911E-6
span
8.5371543073911E-6
Publish a Story
4.1000806871023E-6
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 — 4 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://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
3870
108
https://www.googletagmanager.com/gtag/js?id=G-S8YJPTKXR7&l=dataLayer&cx=c
4170
107
https://www.google-analytics.com/analytics.js
4577
85
https://www.google-analytics.com/analytics.js
636
73
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

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

Metrics

First Contentful Paint — 3.1 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.8 s
The timing of the largest text or image that is painted.
Time to Interactive — 4.3 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 4.0 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5913 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Remove unused CSS — Potential savings of 18 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Nifty.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
19372
18130
Remove unused JavaScript — Potential savings of 21 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-S8YJPTKXR7&l=dataLayer&cx=c
46928
21063

Diagnostics

Serve static assets with an efficient cache policy — 6 resources found
Nifty.org 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.nifty.org/nifty/images/N_132x86.png
0
6138
https://www.nifty.org/nifty/images/gayback.jpg
0
2453
https://www.google-analytics.com/analytics.js
7200000
20199
https://www.google-analytics.com/analytics.js
7200000
20199
https://www.nifty.org/nifty/images/feed-icon-28x28.png
2592000000
2186
https://www.nifty.org/nifty/styles/disclaimer.css
2592000000
1044

Opportunities

Eliminate render-blocking resources — Potential savings of 1,330 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Nifty.org 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://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
19372
930
https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
31013
1080
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
10741
150
Avoid multiple page redirects — Potential savings of 1,890 ms
Redirects can cause additional delays before the page can begin loading. Nifty.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://nifty.org/
630
https://nifty.org/
480
https://www.nifty.org/
780
https://www.nifty.org/nifty/
0

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/fonts/glyphicons-halflings-regular.woff2
23.092000046745
76

Accessibility

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

Tables and lists

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.

Names and labels

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.

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

ARIA

ARIA `progressbar` elements do not 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.
Failing Elements
$3000

Names and labels

Buttons do not 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.
Failing Elements
button
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.

Contrast

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

Tables and lists

`<dl>`'s do not 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.
Failing Elements
Kasey with a K Beginnings Life's Illusions Relationships Miles From Home Colleg…
Newest Stories — the Nifty Archive always welcomes new authors and new or revis…

Navigation

Heading elements are not 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.
Failing Elements
Sections and Selected New Stories

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

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.3.7
jQuery
3.2.1
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://nifty.org/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 8 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
SHOW DETAILS
5
Medium
SHOW DETAILS
3
Medium

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for nifty.org. 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 nifty.org on mobile screens.
Document uses legible font sizes — 99.92% 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
SHOW DETAILS
.label
0.08%
10.5px
SHOW DETAILS
.small, small
0.00%
11.9px
SHOW DETAILS
99.92%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 63% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
Tristan
42x16
My New Friend Craig
Kasey with a K
92x16
Life's Illusions
Life's Illusions
86x16
Miles From Home
Miles From Home
110x16
My New Friend Craig
Beginnings
69x17
Relationships
College
50x17
Relationships
My New Friend Craig
131x16
College
College
50x17
Adult-Friends

Content Best Practices

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

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.
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 nifty.org on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 172.104.9.50
Continent: North America
Country: United States
United States Flag
Region: New Jersey
City: Cedar Knolls
Longitude: -74.4592
Latitude: 40.8229
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Linode
Registration

Domain Registrant

Private Registration: No
Name: Statutory Masking Enabled
Organization: Statutory Masking Enabled
Country: US
City: Statutory Masking Enabled
State: NY
Post Code: Statutory Masking Enabled
Email: abuse@web.com
Phone: Statutory Masking Enabled
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Domains of Origin, LLC 162.159.134.53
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 89/100
WOT Child Safety: 13/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: 1970400181.rsc.cdn77.org
Issued By: R3
Valid From: 17th February, 2021
Valid To: 18th May, 2021
Subject: CN = 1970400181.rsc.cdn77.org
Hash: 88a1fa0f
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x041EC2BEC77205AA89199CCD0FFC6BBCA749
Serial Number (Hex): 041EC2BEC77205AA89199CCD0FFC6BBCA749
Valid From: 17th February, 2024
Valid To: 18th May, 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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Feb 17 02:12:33.964 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:94:1E:C1:68:D2:58:9D:8B:C6:33:50:
FF:24:25:ED:F7:75:9A:3F:1D:0E:5F:92:F6:91:A5:8F:
F9:BE:79:E3:77:02:21:00:BB:C2:CB:19:D9:68:86:55:
BA:36:60:92:27:E8:CE:F2:2C:65:73:9F:4A:13:53:D5:
7E:61:C1:CB:C6:D1:F4:98
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 : Feb 17 02:12:33.937 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:47:C4:A9:BC:A8:B0:F3:49:90:1A:A5:82:
53:EF:2B:94:E5:6C:3D:F4:FA:1B:AC:04:07:59:C8:84:
81:7D:6D:96:02:21:00:CD:A5:2A:8A:F7:BD:E3:CD:D9:
62:96:0B:04:58:75:61:8E:FA:65:63:E1:41:0A:F0:65:
17:97:4C:1E:15:B1:67
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:cdn77.niftyarchive.info
DNS:nifty.nisusnet.com
DNS:www.nifty.org
DNS:1970400181.rsc.cdn77.org
Technical

DNS Lookup

A Records

Host IP Address Class TTL
nifty.org. 172.104.9.50 IN 21599

NS Records

Host Nameserver Class TTL
nifty.org. ns15.dnsmadeeasy.com. IN 21599
nifty.org. ns11.dnsmadeeasy.com. IN 21599
nifty.org. ns13.dnsmadeeasy.com. IN 21599
nifty.org. ns10.dnsmadeeasy.com. IN 21599
nifty.org. ns12.dnsmadeeasy.com. IN 21599
nifty.org. ns14.dnsmadeeasy.com. IN 21599

MX Records

Priority Host Server Class TTL
20 nifty.org. mx2.emailsrvr.com. IN 21599
10 nifty.org. mx1.emailsrvr.com. IN 21599

SOA Records

Domain Name Primary NS Responsible Email TTL
nifty.org. ns10.dnsmadeeasy.com. dns.dnsmadeeasy.com. 21599

TXT Records

Host Value Class TTL
nifty.org. v=spf1 IN 1799
nifty.org. google-site-verification=QTWC1W0vEMIAAqJklGL7Y9s3hRGIyawm8BIxF-Q2n1c IN 1799

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 26th April, 2021
Content-Type: text/html
Cache-Control: max-age=600
Expires: 9th November, 2020
Server: CDN77-Turbo
Content-Length: 1427
Connection: keep-alive
Last-Modified: 20th March, 2017
ETag: "593-54b319b1c8240"
Vary: Accept-Encoding,User-Agent
X-77-NZT: AZySJBbUg1zvfQAAAA==
X-77-NZT-Ray: Jrr/VG5kZ6w=
X-Cache: HIT
X-Age: 125
X-77-POP: newyorkUSNY
X-77-Cache: HIT
Accept-Ranges: bytes

Whois Lookup

Created: 21st May, 1997
Changed: 23rd March, 2021
Expires: 22nd May, 2022
Registrar: Network Solutions, LLC
Status: clientTransferProhibited
Nameservers: ns10.dnsmadeeasy.com
ns11.dnsmadeeasy.com
ns12.dnsmadeeasy.com
ns13.dnsmadeeasy.com
ns14.dnsmadeeasy.com
ns15.dnsmadeeasy.com
Owner Name: Statutory Masking Enabled
Owner Organization: Statutory Masking Enabled
Owner Street: Statutory Masking Enabled
Owner Post Code: Statutory Masking Enabled
Owner City: Statutory Masking Enabled
Owner State: FL
Owner Country: US
Owner Phone: Statutory Masking Enabled
Owner Email: abuse@web.com
Admin Name: Statutory Masking Enabled
Admin Organization: Statutory Masking Enabled
Admin Street: Statutory Masking Enabled
Admin Post Code: Statutory Masking Enabled
Admin City: Statutory Masking Enabled
Admin State: Statutory Masking Enabled
Admin Country: Statutory Masking Enabled
Admin Phone: Statutory Masking Enabled
Admin Email: abuse@web.com
Tech Name: Statutory Masking Enabled
Tech Organization: Statutory Masking Enabled
Tech Street: Statutory Masking Enabled
Tech Post Code: Statutory Masking Enabled
Tech City: Statutory Masking Enabled
Tech State: Statutory Masking Enabled
Tech Country: Statutory Masking Enabled
Tech Phone: Statutory Masking Enabled
Tech Email: abuse@web.com
Billing Name: Statutory Masking Enabled
Billing Organization: Statutory Masking Enabled
Billing Street: Statutory Masking Enabled
Billing Post Code: Statutory Masking Enabled
Billing City: Statutory Masking Enabled
Billing State: Statutory Masking Enabled
Billing Country: Statutory Masking Enabled
Billing Phone: Statutory Masking Enabled
Billing Fax: Statutory Masking Enabled
Billing Email: abuse@web.com
Full Whois: Domain Name: NIFTY.ORG
Registry Domain ID: D263288-LROR
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://www.networksolutions.com
Updated Date: 2021-03-23T07:24:24Z
Creation Date: 1997-05-21T04:00:00Z
Registrar Registration Expiration Date: 2022-05-22T04:00:00Z
Registrar Registration Expiration Date:
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Statutory Masking Enabled
Registrant Name: Statutory Masking Enabled
Registrant Organization: Statutory Masking Enabled
Registrant Street: Statutory Masking Enabled
Registrant City: Statutory Masking Enabled
Registrant State/Province: FL
Registrant Postal Code: Statutory Masking Enabled
Registrant Country: US
Registrant Phone: Statutory Masking Enabled
Registrant Phone Ext: Statutory Masking Enabled
Registrant Fax: Statutory Masking Enabled
Registrant Fax Ext: Statutory Masking Enabled
Registrant Email: abuse@web.com
Registry Admin ID: Statutory Masking Enabled
Admin Name: Statutory Masking Enabled
Admin Organization: Statutory Masking Enabled
Admin Street: Statutory Masking Enabled
Admin City: Statutory Masking Enabled
Admin State/Province: Statutory Masking Enabled
Admin Postal Code: Statutory Masking Enabled
Admin Country: Statutory Masking Enabled
Admin Phone: Statutory Masking Enabled
Admin Phone Ext: Statutory Masking Enabled
Admin Fax: Statutory Masking Enabled
Admin Fax Ext: Statutory Masking Enabled
Admin Email: abuse@web.com
Registry Tech ID: Statutory Masking Enabled
Tech Name: Statutory Masking Enabled
Tech Organization: Statutory Masking Enabled
Tech Street: Statutory Masking Enabled
Tech City: Statutory Masking Enabled
Tech State/Province: Statutory Masking Enabled
Tech Postal Code: Statutory Masking Enabled
Tech Country: Statutory Masking Enabled
Tech Phone: Statutory Masking Enabled
Tech Phone Ext: Statutory Masking Enabled
Tech Fax: Statutory Masking Enabled
Tech Fax Ext: Statutory Masking Enabled
Tech Email: abuse@web.com
Registry Billing ID: Statutory Masking Enabled
Billing Name: Statutory Masking Enabled
Billing Organization: Statutory Masking Enabled
Billing Street: Statutory Masking Enabled
Billing City: Statutory Masking Enabled
Billing State/Province: Statutory Masking Enabled
Billing Postal Code: Statutory Masking Enabled
Billing Country: Statutory Masking Enabled
Billing Phone: Statutory Masking Enabled
Billing Phone Ext: Statutory Masking Enabled
Billing Fax: Statutory Masking Enabled
Billing Fax Ext: Statutory Masking Enabled
Billing Email: abuse@web.com
Name Server: NS10.DNSMADEEASY.COM
Name Server: NS11.DNSMADEEASY.COM
Name Server: NS12.DNSMADEEASY.COM
Name Server: NS13.DNSMADEEASY.COM
Name Server: NS14.DNSMADEEASY.COM
Name Server: NS15.DNSMADEEASY.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8003337680
URL of the ICANN Whois Inaccuracy Complaint Form https: //www.icann.org/wicf/)
>>> Last update of WHOIS database: 2021-04-26T19:10:35Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

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

Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
View Raw Whois

Nameservers

Name IP Address
ns10.dnsmadeeasy.com 208.94.148.4
ns11.dnsmadeeasy.com 208.80.124.4
ns12.dnsmadeeasy.com 208.80.126.4
ns13.dnsmadeeasy.com 208.80.125.4
ns14.dnsmadeeasy.com 208.80.127.4
ns15.dnsmadeeasy.com 208.94.149.4
Related

Subdomains

Domain Subdomain
m.nifty.org
m

Similar Sites

Domain Valuation Snoop Score
adlbooks.com
0/5
assgm.com
$189 USD 1/5
freegaysex.com
0/5
guiltygroups.com
$283 USD
i-cafe.com
0/5
All sites similar to nifty.org

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
nifty.biz
0/5
nifty.com
$6,466,481 USD 5/5
nifty.info
0/5
nifty.net
$27 USD

Sites hosted on the same IP address

Love W3 Snoop?
Update Now

nifty.org Infographic

nifty.org by the numbers infographic

Recently Updated

filmeserialeonline.org
boywankers.com
geography-lesson-5.org
pcsx2.net
indo18.com
tntmagazine.com
desibp.com
dmasti.pk
selenaloca.com
instagram.com

Recently Viewed

receptik.fun
phasmes.com
orthokeratologylenses.com
revivalflame.com
mcginnisdesigns.com
portmeet.com
nehrapi.com
lezzetvakti.com
gamefan.la
pondokkecantikan.com