lexingtonsteele.com

lexingtonsteele.com may not be SSL secured

Free website and domain report on lexingtonsteele.com

Last Updated: 3rd December, 2022 Update Now
Overview

Snoop Summary for lexingtonsteele.com

This is a free and comprehensive report about lexingtonsteele.com. The domain lexingtonsteele.com is currently hosted on a server located in Canada with the IP address 66.152.88.225, where the local currency is CAD and English is the local language. If lexingtonsteele.com was to be sold it would possibly be worth $522 USD (based on the daily revenue potential of the website over a 24 month period). Lexingtonsteele.com receives an estimated 246 unique visitors every day - a decent amount of traffic! This report was last updated 3rd December, 2022.

About lexingtonsteele.com

Site Preview:
Title: Official Website of Lexington Steele | 11 Inch Black Dick
Description: Welcome to the official website of interracial pornstar Lexington Steele! Watch Lex fuck the hottest MILFs and teens with his 11 inch dick in full HD quality!
Keywords and Tags: adult content, pornography
Related Terms: 55 inch tv, 65 inch tv, 75 inch tv, 80 inch tv, 86 inch tv, best 55 inch tv, best 65 inch tv, best 75 inch tv, changhong ruba 55 inch smart tv, peter steele
Fav Icon:
Age: Over 24 years old
Domain Created: 2nd June, 1999
Domain Updated: 13th June, 2022
Domain Expires: 2nd June, 2032
Review

Snoop Score

1/5

Valuation

$522 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 5,598,166
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: 246
Monthly Visitors: 7,487
Yearly Visitors: 89,790
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $21 USD
Yearly Revenue: $256 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: lexingtonsteele.com 19
Domain Name: lexingtonsteele 15
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.79 seconds
Load Time Comparison: Faster than 47% of sites

PageSpeed Insights

Avg. (All Categories) 82
Performance 98
Accessibility 98
Best Practices 83
SEO 100
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
98

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
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).
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 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://lexingtonsteele.com/
http/1.1
0
147.73100009188
240
0
301
text/html
http://www.lexingtonsteele.com/
http/1.1
148.051999975
730.91199994087
9986
13393
200
text/html
Document
https://static01-cms-fame.gammacdn.com/c/minify/fd/8c5dc81edf2c66b8c34c7b098be84e.css
h2
737.50199982896
834.19100008905
2226
6353
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/c/minify/cf/5e072746ea1b4768e6154ea76a5718.css
h2
737.76300018653
815.21600019187
1097
614
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/c/minify/e3/97d196d0a4eabab73f4f6c3b5146f8.css
h2
738.25599998236
797.60400019586
1888
4139
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/c/minify/3c/d52da59ca243c196ab968230ebd909.css
h2
738.39499987662
829.16200021282
5213
17182
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/c/minify/f1/3ee621cfac28cdb3afd590d5be1208.css
h2
738.5419998318
819.14700008929
2108
5268
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/c/minify/ec/406134d23aa6adda333d800cad2ce3.js
h2
738.78300003707
816.19200017303
33176
94965
200
application/javascript
Script
https://static01-cms-fame.gammacdn.com/c/minify/fa/08430f32b19068c225569704dcd8e3.js
h2
738.94099984318
888.83400009945
9806
29475
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-KQVVT4Q
h2
849.59600027651
895.67899983376
91390
278949
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Cabin:700
h2
830.80800017342
848.4359998256
1241
1168
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/eoe652j0gv4kw04w/bgWarningpage.jpg
h2
862.85699997097
964.88500013947
215064
214573
200
image/jpeg
Image
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/d67n0hdp220o8g4o/arrows.png
h2
863.41900005937
907.65599999577
1564
1047
200
image/png
Image
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/bv3fozvh6ko4o04g/Lato-Regular.woff2
h2
864.92000008002
926.60599993542
29921
29388
200
application/font-woff2
Font
https://www.google.com/recaptcha/api.js?onload=showRecaptcha&render=explicit&_=1670070867970
h2
896.64599997923
905.49799986184
1167
908
200
text/javascript
Script
https://www.gstatic.com/recaptcha/releases/Km9gKuG06He-isPsP6saG8cn/recaptcha__en.js
h2
919.74900010973
931.33800011128
163937
408597
200
text/javascript
Script
https://www.google-analytics.com/analytics.js
h2
960.62200004235
965.54600028321
20664
50230
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=993616207&t=pageview&_s=1&dl=http%3A%2F%2Fwww.lexingtonsteele.com%2F&ul=en-us&de=UTF-8&dt=Official%20Website%20of%20Lexington%20Steele%20%7C%2011%20Inch%20Black%20Dick&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAEABAAAAACAAI~&jid=1081394162&gjid=1391546451&cid=340311762.1670070868&tid=UA-129488423-2&_gid=150058526.1670070868&_r=1&gtm=2wgbu0KQVVT4Q&z=961896131
h2
1052.6379998773
1056.6960000433
621
2
200
text/plain
XHR
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=993616207&t=pageview&_s=1&dl=http%3A%2F%2Fwww.lexingtonsteele.com%2F&ul=en-us&de=UTF-8&dt=Official%20Website%20of%20Lexington%20Steele%20%7C%2011%20Inch%20Black%20Dick&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEDAAEABAAAAACAAI~&jid=2012624067&gjid=2053914495&cid=340311762.1670070868&uid=&tid=UA-48231313-1&_gid=150058526.1670070868&_r=1&gtm=2wgbu0KQVVT4Q&z=1380965767
h2
1057.6039999723
1061.776000075
620
1
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-129488423-2&cid=340311762.1670070868&jid=1081394162&gjid=1391546451&_gid=150058526.1670070868&_u=YEBAAEAAAAAAACAAI~&z=664154218
h2
1059.9199999124
1063.984000124
693
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)
735.772
9.056
851.355
10.298
861.661
13.272
893.075
5.311
899.776
14.579
924.129
15.641
944.212
24.691
973.593
7.027
984.221
29.21
1013.477
24.922
1038.435
20.727
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.

Other

Properly size images
Images can slow down the page's load time. Lexingtonsteele.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Lexingtonsteele.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lexingtonsteele.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lexingtonsteele.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lexingtonsteele.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 — Potential savings of 167 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.gstatic.com/recaptcha/releases/Km9gKuG06He-isPsP6saG8cn/recaptcha__en.js
163937
128039
https://www.googletagmanager.com/gtm.js?id=GTM-KQVVT4Q
91390
43101
Efficiently encode images — Potential savings of 34 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/eoe652j0gv4kw04w/bgWarningpage.jpg
214573
34645
Serve images in next-gen formats — Potential savings of 130 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://static01-cms-fame.gammacdn.com/lexingtonsteele/m/eoe652j0gv4kw04w/bgWarningpage.jpg
214573
133335.8
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 580 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://www.lexingtonsteele.com/
583.855
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Lexingtonsteele.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lexingtonsteele.com/
190
http://www.lexingtonsteele.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lexingtonsteele.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.
Avoids enormous network payloads — Total size was 579 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/eoe652j0gv4kw04w/bgWarningpage.jpg
215064
https://www.gstatic.com/recaptcha/releases/Km9gKuG06He-isPsP6saG8cn/recaptcha__en.js
163937
https://www.googletagmanager.com/gtm.js?id=GTM-KQVVT4Q
91390
https://static01-cms-fame.gammacdn.com/c/minify/ec/406134d23aa6adda333d800cad2ce3.js
33176
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/bv3fozvh6ko4o04g/Lato-Regular.woff2
29921
https://www.google-analytics.com/analytics.js
20664
http://www.lexingtonsteele.com/
9986
https://static01-cms-fame.gammacdn.com/c/minify/fa/08430f32b19068c225569704dcd8e3.js
9806
https://static01-cms-fame.gammacdn.com/c/minify/3c/d52da59ca243c196ab968230ebd909.css
5213
https://static01-cms-fame.gammacdn.com/c/minify/fd/8c5dc81edf2c66b8c34c7b098be84e.css
2226
Uses efficient cache policy on static assets — 1 resource found
Lexingtonsteele.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20664
Avoids an excessive DOM size — 61 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
61
Maximum DOM Depth
10
Maximum Child Elements
8
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Lexingtonsteele.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)
Unattributable
51.561
1.601
0
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)
Script Evaluation
103.786
Other
38.53
Rendering
33.383
Style & Layout
21.776
Script Parsing & Compilation
18.891
Parse HTML & CSS
5.931
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 20 requests • 579 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
20
592622
Script
6
320140
Image
2
216628
Font
1
29921
Stylesheet
6
13773
Document
1
9986
Other
4
2174
Media
0
0
Third-party
18
582396
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)
163937
0
91390
0
21905
0
1241
0
1167
0
693
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0001573905644718
0.00012366401494213
8.4732750978866E-5
5.7807028309087E-5
5.2123480147605E-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
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.
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 lexingtonsteele.com on mobile screens.
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.

Budgets

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

Other

Eliminate render-blocking resources — Potential savings of 220 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lexingtonsteele.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://static01-cms-fame.gammacdn.com/c/minify/fd/8c5dc81edf2c66b8c34c7b098be84e.css
2226
230
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of lexingtonsteele.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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate 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"]`
Lexingtonsteele.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
OK

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that lexingtonsteele.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.
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
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.7.2
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 — 2 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://lexingtonsteele.com/
Allowed
http://www.lexingtonsteele.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 6 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
6
Medium
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for lexingtonsteele.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 lexingtonsteele.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.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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.

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of lexingtonsteele.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
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 lexingtonsteele.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.

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
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) 72
Performance 48
Accessibility 98
Best Practices 83
SEO 100
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://m.lexingtonsteele.com/
Updated: 3rd December, 2022

4.03 seconds
First Contentful Paint (FCP)
19%
35%
46%

0.24 seconds
First Input Delay (FID)
3%
95%
2%

48

Performance

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

Metrics

Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Lexingtonsteele.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Lexingtonsteele.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lexingtonsteele.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lexingtonsteele.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lexingtonsteele.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lexingtonsteele.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.
URL Potential Savings (Ms)
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/93h5r5v69cg8kwcc/LS-WarningBg.jpg
0
Avoids enormous network payloads — Total size was 361 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtm.js?id=GTM-KQVVT4Q
91390
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/8p6m6fn6h2kokw0s/roboto-light-webfont.woff
74164
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/93h5r5v69cg8kwcc/LS-WarningBg.jpg
45598
https://static01-cms-fame.gammacdn.com/c/minify/70/4802fede9c2d47fb438a14a8aeb76d.js
33075
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/ra6nrzl5rhwckw4c/roboto-regular-webfont.woff
25595
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/dhrbuxqacg84gcg8/roboto-black-webfont.woff
25180
https://www.google-analytics.com/analytics.js
20664
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/8mk1omnxmp8ow8kk/LS-Logo.png
19427
http://m.lexingtonsteele.com/
9786
https://static01-cms-fame.gammacdn.com/c/minify/cf/e6284a32608a1b9d6686fca852a4e3.js
8979
Uses efficient cache policy on static assets — 2 resources found
Lexingtonsteele.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20664
http://m.lexingtonsteele.com/m/c97pb7l7ghkw0swo/transparent.gif
2592000000
1379
Avoids an excessive DOM size — 68 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
68
Maximum DOM Depth
10
Maximum Child Elements
8
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Lexingtonsteele.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.
Keep request counts low and transfer sizes small — 21 requests • 361 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
21
369481
Script
4
154108
Font
3
124939
Image
3
66404
Stylesheet
5
11379
Document
1
9786
Other
5
2865
Media
0
0
Third-party
17
357379
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0024176905379277
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 — 7 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
5581
396
https://www.googletagmanager.com/gtm.js?id=GTM-KQVVT4Q
3649
328
https://static01-cms-fame.gammacdn.com/c/minify/70/4802fede9c2d47fb438a14a8aeb76d.js
5220
327
https://www.googletagmanager.com/gtm.js?id=GTM-KQVVT4Q
3977
322
Unattributable
630
174
http://m.lexingtonsteele.com/
1969
139
http://m.lexingtonsteele.com/
1890
61
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 lexingtonsteele.com on mobile screens.
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.

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.

Audits

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://lexingtonsteele.com/
http/1.1
0
92.949999962002
229
0
301
text/html
http://www.lexingtonsteele.com/
http/1.1
93.414999777451
382.59099982679
708
0
303
text/html
http://m.lexingtonsteele.com/
http/1.1
383.03299993277
1108.7789998855
9786
13514
200
text/html
Document
https://static01-cms-fame.gammacdn.com/c/minify/51/eebda167de7c1be8bce9fca78c3632.css
h2
1126.8899999559
1194.0999999642
1376
2645
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/c/minify/ed/75e62f1033658816c9bdba356bdd42.css
h2
1127.6469998993
1201.5809998848
1095
612
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/c/minify/a0/7a3581926791b2296e85bd5140ce30.css
h2
1128.0569999944
1193.6519998126
1886
4137
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/c/minify/0b/383d6e9759476647d7ace784fe9b79.css
h2
1129.1249999776
1206.0999998357
4650
22254
200
text/css
Stylesheet
https://static01-cms-fame.gammacdn.com/c/minify/56/f88057154589dc7a46d94f13fef165.css
h2
1129.3949999381
1214.5819999278
2372
5511
200
text/css
Stylesheet
http://m.lexingtonsteele.com/m/c97pb7l7ghkw0swo/transparent.gif
http/1.1
1218.2259999681
1295.9809999447
1379
1099
200
image/gif
Image
https://static01-cms-fame.gammacdn.com/c/minify/70/4802fede9c2d47fb438a14a8aeb76d.js
h2
1209.1209997889
1280.794999795
33075
94963
200
application/javascript
Script
https://static01-cms-fame.gammacdn.com/c/minify/cf/e6284a32608a1b9d6686fca852a4e3.js
h2
1216.5439999662
1238.6949998327
8979
26345
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-KQVVT4Q
h2
1218.3829999994
1282.0249998476
91390
278949
200
application/javascript
Script
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/8mk1omnxmp8ow8kk/LS-Logo.png
h2
1224.3649999145
1280.0929998048
19427
18907
200
image/png
Image
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/93h5r5v69cg8kwcc/LS-WarningBg.jpg
h2
1225.0019998755
1299.8169998173
45598
45110
200
image/jpeg
Image
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/8p6m6fn6h2kokw0s/roboto-light-webfont.woff
h2
1227.3089999799
1288.1739998702
74164
73632
200
application/font-woff
Font
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/dhrbuxqacg84gcg8/roboto-black-webfont.woff
h2
1227.8249999508
1285.0009999238
25180
24648
200
application/font-woff
Font
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/ra6nrzl5rhwckw4c/roboto-regular-webfont.woff
h2
1228.7919998635
1279.415999772
25595
25064
200
application/font-woff
Font
https://www.google-analytics.com/analytics.js
h2
1585.6539998204
1591.7729998473
20664
50230
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=568612860&t=pageview&_s=1&dl=http%3A%2F%2Fm.lexingtonsteele.com%2F&ul=en-us&de=UTF-8&dt=18%2B%20Warning%20%7C%20Lexington%20Steele%20Mobile&sd=24-bit&sr=360x640&vp=640x1137&je=0&_u=YEBAAEABAAAAACAAI~&jid=746950107&gjid=1425236914&cid=834574243.1670070892&tid=UA-129488423-2&_gid=1850819430.1670070892&_r=1&gtm=2wgbu0KQVVT4Q&z=871027243
h2
1690.1539999526
1697.5789999124
619
2
200
text/plain
XHR
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=568612860&t=pageview&_s=1&dl=http%3A%2F%2Fm.lexingtonsteele.com%2F&ul=en-us&de=UTF-8&dt=18%2B%20Warning%20%7C%20Lexington%20Steele%20Mobile&sd=24-bit&sr=360x640&vp=640x1137&je=0&_u=YEDAAEABAAAAACAAI~&jid=162007511&gjid=1651262997&cid=834574243.1670070892&uid=&tid=UA-48231313-1&_gid=1850819430.1670070892&_r=1&gtm=2wgbu0KQVVT4Q&z=1597950267
h2
1707.3709999677
1711.4859998692
618
1
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-129488423-2&cid=834574243.1670070892&jid=746950107&gjid=1425236914&_gid=1850819430.1670070892&_u=YEBAAEAAAAAAACAAI~&z=51828215
h2
1710.1279997732
1714.7569998633
691
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)
1117.337
15.204
1137.766
43.559
1220.741
69.648
1300.976
5.787
1314.755
81.751
1404.456
6.069
1410.613
82.099
1493.248
17.238
1514.232
80.381
1594.626
6.354
1609.862
99.058
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

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

Audits

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

Other

Reduce unused JavaScript — Potential savings of 63 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/gtm.js?id=GTM-KQVVT4Q
91390
43101
https://static01-cms-fame.gammacdn.com/c/minify/70/4802fede9c2d47fb438a14a8aeb76d.js
33075
21515
Serve images in next-gen formats — Potential savings of 19 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://static01-cms-fame.gammacdn.com/lexingtonsteele/m/93h5r5v69cg8kwcc/LS-WarningBg.jpg
45110
19087.45
Reduce JavaScript execution time — 1.5 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.googletagmanager.com/gtm.js?id=GTM-KQVVT4Q
668.296
640.06
23.576
http://m.lexingtonsteele.com/
474.932
24.536
11.232
https://www.google-analytics.com/analytics.js
410.9
392.6
4.564
https://static01-cms-fame.gammacdn.com/c/minify/70/4802fede9c2d47fb438a14a8aeb76d.js
391.584
103.052
272.232
Unattributable
316.732
8.436
0
Minimize main-thread work — 2.3 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
1174.72
Other
396.44
Style & Layout
329.732
Script Parsing & Compilation
314.532
Parse HTML & CSS
42.84
Rendering
28.696
Garbage Collection
13.308

Metrics

First Contentful Paint — 3.4 s
The time taken for the first image or text on the page to be rendered.
Total Blocking Time — 1,000 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).
Largest Contentful Paint — 4.9 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 1,370 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lexingtonsteele.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://static01-cms-fame.gammacdn.com/c/minify/51/eebda167de7c1be8bce9fca78c3632.css
1376
780
https://static01-cms-fame.gammacdn.com/c/minify/ed/75e62f1033658816c9bdba356bdd42.css
1095
150
Reduce initial server response time — Root document took 730 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://m.lexingtonsteele.com/
726.739
Avoid multiple page redirects — Potential savings of 1,260 ms
Redirects can cause additional delays before the page can begin loading. Lexingtonsteele.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lexingtonsteele.com/
630
http://www.lexingtonsteele.com/
630
http://m.lexingtonsteele.com/
0
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://static01-cms-fame.gammacdn.com/lexingtonsteele/m/8p6m6fn6h2kokw0s/roboto-light-webfont.woff
60.864999890327
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/dhrbuxqacg84gcg8/roboto-black-webfont.woff
57.175999972969
https://static01-cms-fame.gammacdn.com/lexingtonsteele/m/ra6nrzl5rhwckw4c/roboto-regular-webfont.woff
50.623999908566
Reduce the impact of third-party code — Third-party code blocked the main thread for 860 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)
91390
520.972
21901
336.232
691
0
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
http://m.lexingtonsteele.com/m/c97pb7l7ghkw0swo/transparent.gif
First Contentful Paint (3G) — 7020 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of lexingtonsteele.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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate 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"]`
Lexingtonsteele.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
OK

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that lexingtonsteele.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.
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
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.7.2
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 — 4 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://lexingtonsteele.com/
Allowed
http://www.lexingtonsteele.com/
Allowed
http://m.lexingtonsteele.com/
Allowed
http://m.lexingtonsteele.com/m/c97pb7l7ghkw0swo/transparent.gif
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 6 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
6
Medium
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for lexingtonsteele.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 lexingtonsteele.com on mobile screens.
Document uses legible font sizes — 100% 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
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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.

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of lexingtonsteele.com. This includes details about web app manifests.

PWA Optimized

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

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
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
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: 66.152.88.225
Continent: North America
Country: Canada
Canada Flag
Region:
City:
Longitude: -79.3716
Latitude: 43.6319
Currencies: CAD
Languages: English
French

Web Hosting Provider

Name IP Address
Gamma Networking Inc.
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
DNC Holdings, Inc 104.143.9.80
Security

Visitor Safety

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

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
lexingtonsteele.com. 66.152.88.225 IN 300

NS Records

Host Nameserver Class TTL
lexingtonsteele.com. ns1.gammanetworking.com. IN 21600
lexingtonsteele.com. ns2.gammanetworking.com. IN 21600

MX Records

Priority Host Server Class TTL
10 lexingtonsteele.com. ge-smtp01.gammae.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
lexingtonsteele.com. ns0.gammanetworking.com. postmaster.gammanetworking.com. 21600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 3rd December, 2022
Content-Type: text/html; charset=utf-8
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
X-Gamma-Serve: pl-php04.gammae.com
content-security-policy: frame-ancestors 'self'
x-frame-options: SAMEORIGIN
Set-Cookie: *
Pragma: no-cache
P3P: CP="NON NID PSAa PSDa OUR IND NAV"
Content-Language: en

Whois Lookup

Created: 2nd June, 1999
Changed: 13th June, 2022
Expires: 2nd June, 2032
Registrar: DNC Holdings, Inc
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
autoRenewPeriod
Nameservers: ns1.gammae.com
ns2.gammae.com
Full Whois:
Domain Name: LEXINGTONSTEELE.COM
Registry Domain ID: 6986043_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.directnic.com
Registrar URL: http://www.directnic.com
Updated Date: 2022-06-13T13:28:20Z
Creation Date: 1999-06-02T14:57:30Z
Registrar Registration Expiration Date: 2032-06-02T14:58:08Z
Registrar: DNC Holdings, Inc
Registrar IANA ID: 291
Registrar Abuse Contact Email: abuse@directnic.com
Registrar Abuse Contact Phone: +1.8778569598
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: autoRenewPeriod (https://www.icann.org/epp#autoRenewPeriod)
Name Server: NS1.GAMMAE.COM
Name Server: NS2.GAMMAE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net
>>> Last update of WHOIS database: 2022-12-03T00:34:24Z <<<


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



The compilation, repackaging, dissemination, or other use of this WHOIS
data is expressly prohibited without the prior written consent of
The Producers, Inc.

The Producers reserves the right to terminate your access to its WHOIS
database in its sole discretion, including without limitation, for
excessive querying of the database or for failure to otherwise abide by
this policy.

The Producers reserves the right to modify these terms at any time.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY.
LACK OF A DOMAIN RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.


Nameservers

Name IP Address
ns1.gammae.com 66.152.92.1
ns2.gammae.com 66.152.92.2
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$14,323 USD 3/5
$324 USD
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

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

Sites hosted on the same IP address

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