Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

avenuemagazine.com

avenuemagazine.com is SSL secured

Free website and domain report on avenuemagazine.com

Last Updated: 25th March, 2022 Update Now
Overview

Snoop Summary for avenuemagazine.com

This is a free and comprehensive report about avenuemagazine.com. Our records indicate that avenuemagazine.com is owned/operated by Charles Cohen. Avenuemagazine.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If avenuemagazine.com was to be sold it would possibly be worth $1,032 USD (based on the daily revenue potential of the website over a 24 month period). Avenuemagazine.com is somewhat popular with an estimated 491 daily unique visitors. This report was last updated 25th March, 2022.

About avenuemagazine.com

Site Preview: avenuemagazine.com avenuemagazine.com
Title:
Description:
Keywords and Tags: blogs, wiki
Related Terms:
Fav Icon:
Age: Over 25 years old
Domain Created: 19th November, 1998
Domain Updated: 19th September, 2019
Domain Expires: 18th November, 2022
Review

Snoop Score

2/5

Valuation

$1,032 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,223,341
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: 491
Monthly Visitors: 14,944
Yearly Visitors: 179,215
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $43 USD
Yearly Revenue: $511 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: avenuemagazine.com 18
Domain Name: avenuemagazine 14
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 3.50 seconds
Load Time Comparison: Faster than 15% of sites

PageSpeed Insights

Avg. (All Categories) 79
Performance 91
Accessibility 77
Best Practices 87
SEO 75
Progressive Web App 64
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://avenuemagazine.com
Updated: 28th September, 2021

1.49 seconds
First Contentful Paint (FCP)
84%
11%
5%

0.00 seconds
First Input Delay (FID)
99%
0%
1%

Simulate loading on desktop
91

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for avenuemagazine.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.
Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
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 — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://avenuemagazine.com/
http/1.1
0
362.85700000008
352
0
301
text/html
https://avenuemagazine.com/
h2
363.55099998764
928.90400000033
16471
106244
200
text/html
Document
https://avenuemagazine.com/user-content/themes/avenue-2020/bootstrap-4.3.1/scss/bootstrap-custom-v1.css
h2
940.81800000276
1009.8770000041
7534
54778
200
text/css
Stylesheet
https://avenuemagazine.com/user-content/themes/avenue-2020/style.css?v=11
h2
940.93099999009
1017.0419999922
6871
39178
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-156221059-1
h2
1018.2389999973
1029.761999991
39703
98490
200
application/javascript
Script
https://avenuemagazine.com/user-content/themes/avenue-2020/img/Avenue-magazine-logo.svg
h2
1020.8519999869
1106.3729999878
822
949
200
image/svg+xml
Image
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
h2
1021.0040000093
1198.9499999909
11686
11456
200
image/jpeg
Image
https://avenuemagazine.com/images/1400_w/2021/09/21/powerlist2021-3526.jpg
h2
1021.2349999929
1155.2399999928
957515
957283
200
image/jpeg
Image
https://avenuemagazine.com/user-content/themes/avenue-2020/img/arrow-down-icon-01.svg
h2
1021.4989999949
1110.5410000018
543
278
200
image/svg+xml
Image
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_290.jpg
h2
1021.670999995
1175.5279999925
7777
7548
200
image/jpeg
Image
https://avenuemagazine.com/user-content/plugins/srgbe-framework-0011-prat-nyl/data/all-scripts-11.js
h2
1011.1239999824
1194.0999999933
731
898
200
application/javascript
Script
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Black.woff2
h2
1033.4929999954
1082.3990000063
48154
47924
200
font/woff2
Font
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickHeadline-Regular-Web.woff2
h2
1033.8089999859
1112.2109999997
92004
91773
200
font/woff2
Font
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickSans-Bold-Web.woff2
h2
1034.0569999826
1109.7080000036
35391
35161
200
font/woff2
Font
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Regular.woff2
h2
1034.2130000063
1172.3869999987
45790
45560
200
font/woff2
Font
https://www.google-analytics.com/analytics.js
h2
1104.9009999842
1110.0729999889
20399
49529
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j93&a=475955124&t=pageview&_s=1&dl=https%3A%2F%2Favenuemagazine.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%7C%20Avenue%20Magazine&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=1970429109&gjid=871094709&cid=2058641128.1632852924&tid=UA-156221059-1&_gid=1020469486.1632852924&_r=1&gtm=2ou9r0&z=372853808
h2
1152.1049999865
1156.1109999893
643
1
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)
963.578
6.063
1051.61
5.284
1056.904
36.996
1107.296
7.398
1118.353
9.847
1128.211
7.767
1151.431
5.148
1156.971
9.99
1167.06
17.474
1217.11
7.712
1227.268
17.787
2235.135
21.262
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Avenuemagazine.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 141 KiB
Images can slow down the page's load time. Avenuemagazine.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://avenuemagazine.com/images/1400_w/2021/09/21/powerlist2021-3526.jpg
957283
129435
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
11456
9778
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_290.jpg
7548
5615
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Avenuemagazine.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Avenuemagazine.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Avenuemagazine.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Avenuemagazine.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 570 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://avenuemagazine.com/
566.343
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Avenuemagazine.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://avenuemagazine.com/
190
https://avenuemagazine.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Avenuemagazine.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 1,262 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://avenuemagazine.com/images/1400_w/2021/09/21/powerlist2021-3526.jpg
957515
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickHeadline-Regular-Web.woff2
92004
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Black.woff2
48154
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Regular.woff2
45790
https://www.googletagmanager.com/gtag/js?id=UA-156221059-1
39703
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickSans-Bold-Web.woff2
35391
https://www.google-analytics.com/analytics.js
20399
https://avenuemagazine.com/
16471
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
11686
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_290.jpg
7777
Avoids an excessive DOM size — 684 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
684
Maximum DOM Depth
In America: A Lexicon of Fashion
16
Maximum Child Elements
CULTURE Inside the Dual Jasper Johns Exhibits in NYC and Philadelphia CULTURE N…
39
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. Avenuemagazine.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://avenuemagazine.com/
134.351
18.52
2.341
Unattributable
58.82
2.289
0.182
Minimizes main-thread work — 0.2 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)
Style & Layout
67.919
Script Evaluation
52.445
Other
52.128
Rendering
46.448
Parse HTML & CSS
10.391
Script Parsing & Compilation
5.253
Keep request counts low and transfer sizes small — 17 requests • 1,262 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
17
1292386
Image
5
978343
Font
4
221339
Script
3
60833
Document
1
16471
Stylesheet
2
14405
Other
2
995
Media
0
0
Third-party
3
60745
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
39703
0
SHOW DETAILS
21042
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
div.row > div.col-12 > picture > img.full-width
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
div.row > div.col-12 > picture > img.full-width
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 avenuemagazine.com on mobile screens.

Budgets

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

Metrics

Speed Index — 1.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.7 s
The timing of the largest text or image that is painted.

Opportunities

Efficiently encode images — Potential savings of 603 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://avenuemagazine.com/images/1400_w/2021/09/21/powerlist2021-3526.jpg
957283
612802
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
11456
4970
Serve images in next-gen formats — Potential savings of 788 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://avenuemagazine.com/images/1400_w/2021/09/21/powerlist2021-3526.jpg
957283
797673.95
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
11456
8924.9

Diagnostics

Serve static assets with an efficient cache policy — 13 resources found
Avenuemagazine.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://avenuemagazine.com/images/1400_w/2021/09/21/powerlist2021-3526.jpg
0
957515
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickHeadline-Regular-Web.woff2
0
92004
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Black.woff2
0
48154
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Regular.woff2
0
45790
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickSans-Bold-Web.woff2
0
35391
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
0
11686
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_290.jpg
0
7777
https://avenuemagazine.com/user-content/themes/avenue-2020/bootstrap-4.3.1/scss/bootstrap-custom-v1.css
0
7534
https://avenuemagazine.com/user-content/themes/avenue-2020/style.css?v=11
0
6871
https://avenuemagazine.com/user-content/themes/avenue-2020/img/Avenue-magazine-logo.svg
0
822
https://avenuemagazine.com/user-content/plugins/srgbe-framework-0011-prat-nyl/data/all-scripts-11.js
0
731
https://avenuemagazine.com/user-content/themes/avenue-2020/img/arrow-down-icon-01.svg
0
543
https://www.google-analytics.com/analytics.js
7200000
20399
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://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Black.woff2
48.906000010902
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickHeadline-Regular-Web.woff2
78.402000013739
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickSans-Bold-Web.woff2
75.651000021026
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Regular.woff2
138.17399999243
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://avenuemagazine.com/images/1400_w/2021/09/21/powerlist2021-3526.jpg
div.row > div.col-12 > picture > img.full-width
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
div.col-8 > div#top-logo-lower > a.d-block > img.full-width
https://avenuemagazine.com/user-content/themes/avenue-2020/img/arrow-down-icon-01.svg
div.col-12 > a#TeaserGridElement_load-more-button-1 > div.margin-0-auto > img.full-width
https://avenuemagazine.com/user-content/themes/avenue-2020/img/Avenue-magazine-logo.svg
div.colset-2 > div#top-logo > a.d-block > img.full-width
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_290.jpg
div.row > div.col-12 > a.d-block > img.full-width
77

Accessibility

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

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

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
CULTURE
CULTURE
EVENTS
CULTURE
LIVING
CULTURE
STYLE
STYLE
CULTURE
CITY LIFE
CITY LIFE
EVENTS
CITY LIFE
EVENTS
CITY LIFE
EVENTS
STYLE
STYLE
EVENTS
EVENTS
EVENTS
EVENTS
STYLE
CULTURE
CITY LIFE
CITY LIFE
EVENTS
STYLE
STYLE
LIVING
CITY LIFE
CITY LIFE
CITY LIFE
LIVING
CITY LIFE
CITY LIFE
CITY LIFE
NEWS
NEWS
© 2021 Cohen Media Publications LLC. All rights reserved.

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.colset-2 > div#top-logo > a.d-block > img.full-width
div.col-8 > div#top-logo-lower > a.d-block > img.full-width
div.row > div.col-12 > picture > img.full-width
div.col-12 > a#TeaserGridElement_load-more-button-1 > div.margin-0-auto > img.full-width
div.row > div.col-12 > a.d-block > img.full-width
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 avenuemagazine.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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://avenuemagazine.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
75

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of avenuemagazine.com 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.
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.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.colset-2 > div#top-logo > a.d-block > img.full-width
div.col-8 > div#top-logo-lower > a.d-block > img.full-width
div.row > div.col-12 > picture > img.full-width
div.col-12 > a#TeaserGridElement_load-more-button-1 > div.margin-0-auto > img.full-width
div.row > div.col-12 > a.d-block > img.full-width

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.

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

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 avenuemagazine.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.
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 avenuemagazine.com on 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
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) 77
Performance 75
Accessibility 77
Best Practices 87
SEO 77
Progressive Web App 67
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://avenuemagazine.com
Updated: 28th September, 2021

1.48 seconds
First Contentful Paint (FCP)
84%
11%
5%

0.01 seconds
First Input Delay (FID)
98%
2%
0%

Simulate loading on mobile
75

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for avenuemagazine.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.
Total Blocking Time — 30 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
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 — 100 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.3 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://avenuemagazine.com/
http/1.1
0
388.51499999873
368
0
301
text/html
https://avenuemagazine.com/
h2
389.4319999963
1225.7519999985
16471
106244
200
text/html
Document
https://avenuemagazine.com/user-content/themes/avenue-2020/bootstrap-4.3.1/scss/bootstrap-custom-v1.css
h2
1258.9180000068
1327.7459999954
7534
54778
200
text/css
Stylesheet
https://avenuemagazine.com/user-content/themes/avenue-2020/style.css?v=11
h2
1259.3000000052
1395.319999996
6871
39178
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-156221059-1
h2
1396.6660000006
1411.1899999989
39703
98490
200
application/javascript
Script
https://avenuemagazine.com/user-content/themes/avenue-2020/img/Avenue-magazine-logo.svg
h2
1399.7999999992
1584.5379999955
822
949
200
image/svg+xml
Image
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
h2
1399.9900000053
1427.5330000091
11686
11456
200
image/jpeg
Image
https://avenuemagazine.com/images/767_w/2021/09/21/powerlist2021-3526.jpg
h2
1400.1280000084
1587.0910000085
326780
326548
200
image/jpeg
Image
https://avenuemagazine.com/user-content/themes/avenue-2020/img/arrow-down-icon-01.svg
h2
1400.2429999964
1473.5630000068
543
278
200
image/svg+xml
Image
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_290.jpg
h2
1400.4390000046
1423.7330000033
7777
7548
200
image/jpeg
Image
https://avenuemagazine.com/user-content/plugins/srgbe-framework-0011-prat-nyl/data/all-scripts-11.js
h2
1329.3189999968
1458.0600000045
731
898
200
application/javascript
Script
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickHeadline-Regular-Web.woff2
h2
1415.279000008
1474.463999999
92004
91773
200
font/woff2
Font
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickSans-Bold-Web.woff2
h2
1415.6240000011
1516.1990000051
35391
35161
200
font/woff2
Font
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Regular.woff2
h2
1415.8940000052
1468.5020000034
45790
45560
200
font/woff2
Font
https://www.google-analytics.com/analytics.js
h2
1531.25
1535.6440000032
20399
49529
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j93&a=723528387&t=pageview&_s=1&dl=https%3A%2F%2Favenuemagazine.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%7C%20Avenue%20Magazine&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=95925097&gjid=572252953&cid=1484640669.1632852941&tid=UA-156221059-1&_gid=315740218.1632852941&_r=1&gtm=2ou9r0&z=874662366
h2
1586.5720000002
1592.2510000091
643
1
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)
1259.993
11.221
1428.454
7.23
1435.697
40.033
1482.178
6.241
1489.884
27.35
1517.291
9.74
1534.553
16.161
1550.819
10.718
1562.456
6.106
1572.391
12.694
1591.436
25.791
2506.057
12.395
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.
First Contentful Paint (3G) — 2556 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Avenuemagazine.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. Avenuemagazine.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Avenuemagazine.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Avenuemagazine.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Avenuemagazine.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Avenuemagazine.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Avenuemagazine.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://avenuemagazine.com/
630
https://avenuemagazine.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Avenuemagazine.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 599 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://avenuemagazine.com/images/767_w/2021/09/21/powerlist2021-3526.jpg
326780
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickHeadline-Regular-Web.woff2
92004
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Regular.woff2
45790
https://www.googletagmanager.com/gtag/js?id=UA-156221059-1
39703
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickSans-Bold-Web.woff2
35391
https://www.google-analytics.com/analytics.js
20399
https://avenuemagazine.com/
16471
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
11686
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_290.jpg
7777
https://avenuemagazine.com/user-content/themes/avenue-2020/bootstrap-4.3.1/scss/bootstrap-custom-v1.css
7534
Avoids an excessive DOM size — 684 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
684
Maximum DOM Depth
In America: A Lexicon of Fashion
16
Maximum Child Elements
CULTURE Inside the Dual Jasper Johns Exhibits in NYC and Philadelphia CULTURE N…
39
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Avenuemagazine.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.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://avenuemagazine.com/
648.172
113.308
14.932
Unattributable
226.944
16.876
0.972
https://www.google-analytics.com/analytics.js
108.896
97.248
5.624
https://www.googletagmanager.com/gtag/js?id=UA-156221059-1
90.516
77.736
7.444
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
308.468
Style & Layout
299.892
Other
254.432
Rendering
149.868
Parse HTML & CSS
61.024
Script Parsing & Compilation
29.584
Keep request counts low and transfer sizes small — 16 requests • 599 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
16
613513
Image
5
347608
Font
3
173185
Script
3
60833
Document
1
16471
Stylesheet
2
14405
Other
2
1011
Media
0
0
Third-party
3
60745
Minimize third-party usage — Third-party code blocked the main thread for 40 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
21042
42.956
SHOW DETAILS
39703
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
div.row > div.col-12 > picture > img.full-width
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
div.row > div.col-12 > picture > img.full-width
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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://www.google-analytics.com/analytics.js
3563
103
https://avenuemagazine.com/
1321
80
https://avenuemagazine.com/user-content/plugins/srgbe-framework-0011-prat-nyl/data/all-scripts-11.js
5310
55
Unattributable
630
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of avenuemagazine.com on mobile screens.

Budgets

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

Metrics

Speed Index — 5.1 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 4.5 s
The time taken for the page to become fully interactive.

Metrics

Largest Contentful Paint — 5.2 s
The timing of the largest text or image that is painted.

Opportunities

Efficiently encode images — Potential savings of 203 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://avenuemagazine.com/images/767_w/2021/09/21/powerlist2021-3526.jpg
326548
203379
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
11456
4970
Serve images in next-gen formats — Potential savings of 270 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://avenuemagazine.com/images/767_w/2021/09/21/powerlist2021-3526.jpg
326548
267956.55
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
11456
8924.9
Reduce initial server response time — Root document took 840 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://avenuemagazine.com/
837.313

Diagnostics

Serve static assets with an efficient cache policy — 12 resources found
Avenuemagazine.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://avenuemagazine.com/images/767_w/2021/09/21/powerlist2021-3526.jpg
0
326780
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickHeadline-Regular-Web.woff2
0
92004
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Regular.woff2
0
45790
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickSans-Bold-Web.woff2
0
35391
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
0
11686
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_290.jpg
0
7777
https://avenuemagazine.com/user-content/themes/avenue-2020/bootstrap-4.3.1/scss/bootstrap-custom-v1.css
0
7534
https://avenuemagazine.com/user-content/themes/avenue-2020/style.css?v=11
0
6871
https://avenuemagazine.com/user-content/themes/avenue-2020/img/Avenue-magazine-logo.svg
0
822
https://avenuemagazine.com/user-content/plugins/srgbe-framework-0011-prat-nyl/data/all-scripts-11.js
0
731
https://avenuemagazine.com/user-content/themes/avenue-2020/img/arrow-down-icon-01.svg
0
543
https://www.google-analytics.com/analytics.js
7200000
20399
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://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickHeadline-Regular-Web.woff2
59.184999990975
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/ChiswickSans-Bold-Web.woff2
100.57500000403
https://avenuemagazine.com/user-content/themes/avenue-2020/fonts/LabGrotesque-Regular.woff2
52.607999998145
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://avenuemagazine.com/images/767_w/2021/09/21/powerlist2021-3526.jpg
div.row > div.col-12 > picture > img.full-width
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_424.jpg
div.col-8 > div#top-logo-lower > a.d-block > img.full-width
https://avenuemagazine.com/user-content/themes/avenue-2020/img/arrow-down-icon-01.svg
div.col-12 > a#TeaserGridElement_load-more-button-1 > div.margin-0-auto > img.full-width
https://avenuemagazine.com/user-content/themes/avenue-2020/img/AVENUE_logoICON_RGB_290.jpg
div.row > div.col-12 > a.d-block > img.full-width
77

Accessibility

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

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

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
CULTURE
CULTURE
EVENTS
CULTURE
LIVING
CULTURE
STYLE
STYLE
CULTURE
CITY LIFE
CITY LIFE
EVENTS
CITY LIFE
EVENTS
CITY LIFE
EVENTS
STYLE
STYLE
EVENTS
EVENTS
EVENTS
EVENTS
STYLE
CULTURE
CITY LIFE
CITY LIFE
EVENTS
STYLE
STYLE
LIVING
CITY LIFE
CITY LIFE
CITY LIFE
LIVING
CITY LIFE
CITY LIFE
CITY LIFE
NEWS
NEWS
© 2021 Cohen Media Publications LLC. All rights reserved.

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.col-8 > div#top-logo-lower > a.d-block > img.full-width
div.row > div.col-12 > picture > img.full-width
div.col-12 > a#TeaserGridElement_load-more-button-1 > div.margin-0-auto > img.full-width
div.row > div.col-12 > a.d-block > img.full-width
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 avenuemagazine.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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://avenuemagazine.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
77

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of avenuemagazine.com on mobile screens.
Document uses legible font sizes — 95.45% 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
.font-sm
3.88%
11.76px
SHOW DETAILS
.font-xs
0.67%
10.92px
SHOW DETAILS
95.45%
≥ 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.
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

Tap targets are not sized appropriately — 88% 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
STYLE
42x14
DIGITAL ISSUE
EVENTS
53x14
CITY LIFE
LIVING
46x14
CONTACT
CULTURE
62x14
DIGITAL ISSUE

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.col-8 > div#top-logo-lower > a.d-block > img.full-width
div.row > div.col-12 > picture > img.full-width
div.col-12 > a#TeaserGridElement_load-more-button-1 > div.margin-0-auto > img.full-width
div.row > div.col-12 > a.d-block > img.full-width

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.

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

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 avenuemagazine.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.
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 avenuemagazine.com on 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
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:
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Media Temple, Inc.
Registration

Domain Registrant

Private Registration: No
Name: Charles Cohen
Organization: Charles Cohen
Country: US
City: NEW YORK
State: NY
Post Code: 10022-1200
Email: amanzo@cohenbrothers.com
Phone: +1.6467231774
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Network Solutions, LLC 162.159.133.53
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: avenuemagazine.com
Issued By: R3
Valid From: 8th September, 2021
Valid To: 7th December, 2021
Subject: CN = avenuemagazine.com
Hash: 82a638f9
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03DE7B8074E3C1C1E15D7A879E7EDF3DDC5E
Serial Number (Hex): 03DE7B8074E3C1C1E15D7A879E7EDF3DDC5E
Valid From: 8th September, 2024
Valid To: 7th December, 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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Sep 9 00:53:14.654 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C8:24:D7:24:BC:6D:B9:44:AD:E8:BE:
56:3F:01:66:D7:CF:77:C5:C4:37:39:C8:30:AC:75:97:
12:59:B3:90:12:02:21:00:DD:10:86:7B:7D:62:F0:76:
A4:D3:FA:75:7D:92:75:14:47:37:5D:00:D8:B7:F3:2D:
83:DF:65:85:92:E2:34:F0
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Sep 9 00:53:14.648 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:16:3E:FA:FD:D9:29:5E:C3:74:9D:14:9F:
35:C5:73:8E:FC:5D:37:A0:C9:B9:B2:C8:52:3C:47:24:
90:77:73:73:02:21:00:90:BC:D0:2C:65:DB:87:B6:31:
77:C3:98:EE:FB:CC:41:8F:EC:F0:6B:9B:BE:9F:AA:27:
C1:C2:09:C5:C0:C6:3A
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.avenuemagazine.com
DNS:avenuemagazine.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 28th September, 2021
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: User-Agent
X-Powered-By: PleskLin
Link: <https://avenuemagazine.com/wp-json/>; rel="https://api.w.org/", <https://avenuemagazine.com/>; rel=shortlink

Whois Lookup

Created: 19th November, 1998
Changed: 19th September, 2019
Expires: 18th November, 2022
Registrar: Network Solutions, LLC
Status: ok
Nameservers: ns1.mediatemple.net
ns2.mediatemple.net
Owner Name: Charles Cohen
Owner Organization: Charles Cohen
Owner Street: 750 LEXINGTON AVE
Owner Post Code: 10022-1200
Owner City: NEW YORK
Owner State: NY
Owner Country: US
Owner Phone: +1.6467231774
Owner Email: amanzo@cohenbrothers.com
Admin Name: Charles Cohen
Admin Organization: Charles Cohen
Admin Street: 750 LEXINGTON AVE
Admin Post Code: 10022-1200
Admin City: NEW YORK
Admin State: NY
Admin Country: US
Admin Phone: +1.6467231774
Admin Email: amanzo@cohenbrothers.com
Tech Name: Charles Cohen
Tech Organization: Charles Cohen
Tech Street: 750 LEXINGTON AVE
Tech Post Code: 10022-1200
Tech City: NEW YORK
Tech State: NY
Tech Country: US
Tech Phone: +1.6467231774
Tech Email: amanzo@cohenbrothers.com
Full Whois: Domain Name: AVENUEMAGAZINE.COM
Registry Domain ID: 5256188_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://networksolutions.com
Updated Date: 2019-09-19T06:59:10Z
Creation Date: 1998-11-19T05:00:00Z
Registrar Registration Expiration Date: 2022-11-18T05:00:00Z
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Reseller:
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID:
Registrant Name: Charles Cohen
Registrant Organization: Charles Cohen
Registrant Street: 750 LEXINGTON AVE
Registrant City: NEW YORK
Registrant State/Province: NY
Registrant Postal Code: 10022-1200
Registrant Country: US
Registrant Phone: +1.6467231774
Registrant Phone Ext:
Registrant Fax: +1.9999999999
Registrant Fax Ext:
Registrant Email: amanzo@cohenbrothers.com
Registry Admin ID:
Admin Name: Charles Cohen
Admin Organization: Charles Cohen
Admin Street: 750 LEXINGTON AVE
Admin City: NEW YORK
Admin State/Province: NY
Admin Postal Code: 10022-1200
Admin Country: US
Admin Phone: +1.6467231774
Admin Phone Ext:
Admin Fax: +1.9999999999
Admin Fax Ext:
Admin Email: amanzo@cohenbrothers.com
Registry Tech ID:
Tech Name: Charles Cohen
Tech Organization: Charles Cohen
Tech Street: 750 LEXINGTON AVE
Tech City: NEW YORK
Tech State/Province: NY
Tech Postal Code: 10022-1200
Tech Country: US
Tech Phone: +1.6467231774
Tech Phone Ext:
Tech Fax: +1.9999999999
Tech Fax Ext:
Tech Email: amanzo@cohenbrothers.com
Name Server: NS1.MEDIATEMPLE.NET
Name Server: NS2.MEDIATEMPLE.NET
DNSSEC: unsigned
Registrar Abuse Contact Email: domain.operations@web.com
Registrar Abuse Contact Phone: +1.8777228662
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-03-25T18:04:29Z <<<

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


The data in Networksolutions.com's WHOIS database is provided to you by
Networksolutions.com for information purposes only, that is, to assist you in
obtaining information about or related to a domain name registration
record. Networksolutions.com makes this information available "as is," and
does not guarantee its accuracy. By submitting a WHOIS query, you
agree that you will use this data only for lawful purposes and that,
under no circumstances will you use this data to: (1) allow, enable,
or otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via direct mail, electronic mail, or by
telephone; or (2) enable high volume, automated, electronic processes
that apply to Networksolutions.com (or its systems). The compilation,
repackaging, dissemination or other use of this data is expressly
prohibited without the prior written consent of Networksolutions.com.
Networksolutions.com reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

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

Nameservers

Name IP Address
ns1.mediatemple.net 97.74.100.1
ns2.mediatemple.net 173.201.68.1
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
avenuemagazine.ca
0/5

Sites hosted on the same IP address

Love W3 Snoop?
Update Now

Recently Updated

payonwallet.biz
jjcam.cc
freeserials.com
crictorrents.com
zipbuy.net
fotokid.net
vimeocdn.com
lolihub.com
politikfilm.net
tamilrockers.com

Recently Viewed

thecityoflights.net
cosmeticare.com
szbbw.net
svcic.com
tvdir.net
fgbss.com
aaaacccc.com
l-eco.fr
cloudq.net
csengineermag.com