fontmeme.com

fontmeme.com is SSL secured

Free website and domain report on fontmeme.com

Last Updated: 4th October, 2022 Update Now
Overview

Snoop Summary for fontmeme.com

This is a free and comprehensive report about fontmeme.com. The domain fontmeme.com is currently hosted on a server located in United States with the IP address 104.26.2.12, where the local currency is USD and English is the local language. Our records indicate that fontmeme.com is owned/operated by Domain Protection Services, Inc.. Fontmeme.com is expected to earn an estimated $1,791 USD per day from advertising revenue. The sale of fontmeme.com would possibly be worth $1,307,441 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Fontmeme.com receives an estimated 285,422 unique visitors every day - an insane amount of traffic! This report was last updated 4th October, 2022.

About fontmeme.com

Site Preview: fontmeme.com fontmeme.com
Title: Font Meme: Fonts & Typography Resource
Description: Fonts & typography resource where you can generate text with fonts, discover fonts used in logos, movies, books etc, get your fonts identified and more.
Keywords and Tags: hardware, software
Related Terms: best fonts, fonts for free, free beautiful fonts, free cool fonts, free internet fonts, internet fonts, online fonts, real fonts, sans fonts, serif fonts
Fav Icon:
Age: Over 12 years old
Domain Created: 3rd January, 2012
Domain Updated: 16th February, 2020
Domain Expires: 3rd January, 2026
Review

Snoop Score

4/5 (Excellent!)

Valuation

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

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,618
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: 285,422
Monthly Visitors: 8,687,347
Yearly Visitors: 104,179,030
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1,791 USD
Monthly Revenue: $54,512 USD
Yearly Revenue: $653,715 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: fontmeme.com 12
Domain Name: fontmeme 8
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.23 seconds
Load Time Comparison: Faster than 72% of sites

PageSpeed Insights

Avg. (All Categories) 80
Performance 98
Accessibility 70
Best Practices 85
SEO 100
Progressive Web App 48
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://fontmeme.com/
Updated: 29th July, 2020

1.71 seconds
First Contentful Paint (FCP)
46%
45%
9%

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

Simulate loading on desktop
98

Performance

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

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.5 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

First CPU Idle — 0.5 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.5 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive fontmeme.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://fontmeme.com/
0
151.90400020219
591
0
301
text/html
https://fontmeme.com/
152.32100011781
393.02700012922
4176
23939
200
text/html
Document
https://fontmeme.com/assets/sidebar-bg340.png
413.20800012909
480.10700009763
678
93
200
image/png
Image
https://fontmeme.com/global/fonts/oswald-v11-latin-ext_latin-regular.woff2
414.19999999925
435.34000008367
20617
20092
200
application/octet-stream
Font
https://fontmeme.com/assets/style.css
418.51000022143
501.14000006579
15495
69353
200
text/css
Stylesheet
https://fontmeme.com/assets/logo.png
481.52500018477
502.6150001213
7522
6933
200
image/png
Image
https://fontmeme.com/images/gacha-life-font-x-370x370.jpg
508.01400002092
540.52400006913
47324
46734
200
image/jpeg
Image
https://fontmeme.com/images/sekiro-shadows-die-twice-fontmeme-font-370x370.jpg
512.15200009756
536.70600010082
25609
25018
200
image/jpeg
Image
https://fontmeme.com/images/castle-crashers-font-370x370.jpg
513.38100014254
578.28500005417
36578
35987
200
image/jpeg
Image
https://fontmeme.com/images/Todays-Golfer-UK-May-2020-typeface-370x523.jpg
515.36800013855
546.88000003807
60314
59723
200
image/jpeg
Image
https://fontmeme.com/images/rough-and-rowdy-ways-font-370x370.jpg
517.75000011548
569.62700001895
23445
22854
200
image/jpeg
Image
https://fontmeme.com/images/bfdi-logo-370x370.png
518.00500019453
589.90500005893
79836
79260
200
image/png
Image
https://fontmeme.com/images/deltarune-game-font-370x370.jpg
518.80600000732
577.33400003053
23344
22753
200
image/jpeg
Image
https://fontmeme.com/images/vast-of-night-poster-fm-370x548.jpg
518.9740001224
575.69600013085
39839
39248
200
image/jpeg
Image
https://fontmeme.com/images/outer-banks-tv-1-370x548.jpg
519.10600019619
580.68200014532
47588
46997
200
image/jpeg
Image
https://fontmeme.com/images/tiger-king-font-370x548.jpg
519.71200015396
576.509000035
64729
64138
200
image/jpeg
Image
https://fontmeme.com/images/mrs-america-font-370x463.jpg
522.50000019558
588.6129999999
24029
23438
200
image/jpeg
Image
https://fontmeme.com/images/beastie-boys-story-font-370x555.jpg
522.7390001528
583.64200009964
40215
39624
200
image/jpeg
Image
https://fontmeme.com/images/frighteners_movie_font-370x550.jpg
522.92000013404
580.07000014186
14741
14150
200
image/jpeg
Image
https://fontmeme.com/images/ahs-1984-font-370x556.jpg
523.31400010735
578.7400000263
44015
43424
200
image/jpeg
Image
https://fontmeme.com/images/grief-recovery-method-font-370x370.png
523.47900019959
576.94900012575
13841
13251
200
image/png
Image
https://fontmeme.com/images/Spoonflower-font-370x370.jpg
523.62600015476
590.94900009222
8250
7660
200
image/jpeg
Image
https://fontmeme.com/images/kerrang-font-370x502.jpg
524.83000000939
577.87400018424
55050
54459
200
image/jpeg
Image
https://fontmeme.com/images/garnet-hill-logo-font-370x370.png
525.02700011246
579.13000020199
13609
13019
200
image/png
Image
https://fontmeme.com/images/get-weird-deluxe-font-370x370.jpg
525.16800002195
619.1000000108
39478
38887
200
image/jpeg
Image
https://fontmeme.com/images/jackbox-games-logo-font-370x370.png
525.32300003804
577.61800009757
17814
17224
200
image/png
Image
https://fontmeme.com/images/HRB-logo-font-370x370.png
525.46600019559
604.40700012259
16216
15626
200
image/png
Image
https://fontmeme.com/images/disocery-family-font-370x370.png
526.65200014599
584.64500005357
22797
22207
200
image/png
Image
https://fontmeme.com/images/orange-box-font-370x469.jpg
527.92300004512
581.88800001517
37104
36513
200
image/jpeg
Image
https://fontmeme.com/images/plaints-trains-automobiles-font-1-370x559.jpg
528.0910001602
616.61800020374
47174
46583
200
image/jpeg
Image
https://www.google-analytics.com/analytics.js
528.22400000878
539.2990000546
19085
45958
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j83&a=2136855107&t=pageview&_s=1&dl=https%3A%2F%2Ffontmeme.com%2F&ul=en-us&de=UTF-8&dt=Font%20Meme%3A%20Fonts%20%26%20Typography%20Resource&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEAB~&jid=1265177326&gjid=1678289824&cid=491382661.1596012480&tid=UA-31486302-1&_gid=1139181172.1596012480&_r=1&z=1477864222
678.68200014345
682.45600000955
576
35
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
430.374
12.103
447.466
6.303
535.247
5.706
542.383
33.043
575.442
51.585
651.672
7.437
663.467
9.515
673.197
37.228
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 100 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fontmeme.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://fontmeme.com/assets/style.css
15495
110
Properly size images — Potential savings of 246 KiB
Images can slow down the page's load time. Fontmeme.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://fontmeme.com/images/bfdi-logo-370x370.png
79260
23622
https://fontmeme.com/images/tiger-king-font-370x548.jpg
64138
19128
https://fontmeme.com/images/Todays-Golfer-UK-May-2020-typeface-370x523.jpg
59723
17817
https://fontmeme.com/images/kerrang-font-370x502.jpg
54459
16193
https://fontmeme.com/images/outer-banks-tv-1-370x548.jpg
46997
14016
https://fontmeme.com/images/gacha-life-font-x-370x370.jpg
46734
13928
https://fontmeme.com/images/plaints-trains-automobiles-font-1-370x559.jpg
46583
13908
https://fontmeme.com/images/ahs-1984-font-370x556.jpg
43424
12931
https://fontmeme.com/images/beastie-boys-story-font-370x555.jpg
39624
11809
https://fontmeme.com/images/vast-of-night-poster-fm-370x548.jpg
39248
11705
https://fontmeme.com/images/get-weird-deluxe-font-370x370.jpg
38887
11589
https://fontmeme.com/images/orange-box-font-370x469.jpg
36513
10878
https://fontmeme.com/images/castle-crashers-font-370x370.jpg
35987
10725
https://fontmeme.com/images/sekiro-shadows-die-twice-fontmeme-font-370x370.jpg
25018
7456
https://fontmeme.com/images/mrs-america-font-370x463.jpg
23438
6982
https://fontmeme.com/images/rough-and-rowdy-ways-font-370x370.jpg
22854
6811
https://fontmeme.com/images/deltarune-game-font-370x370.jpg
22753
6781
https://fontmeme.com/images/disocery-family-font-370x370.png
22207
6618
https://fontmeme.com/images/jackbox-games-logo-font-370x370.png
17224
5133
https://fontmeme.com/assets/logo.png
6933
4942
https://fontmeme.com/images/HRB-logo-font-370x370.png
15626
4657
https://fontmeme.com/images/frighteners_movie_font-370x550.jpg
14150
4213
https://fontmeme.com/images/grief-recovery-method-font-370x370.png
13251
3949
https://fontmeme.com/images/garnet-hill-logo-font-370x370.png
13019
3880
https://fontmeme.com/images/Spoonflower-font-370x370.jpg
7660
2283
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fontmeme.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fontmeme.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://fontmeme.com/assets/style.css
15495
2568
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fontmeme.com should consider minifying JS files.
Remove unused CSS — Potential savings of 14 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fontmeme.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://fontmeme.com/assets/style.css
15495
14085
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 153 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://fontmeme.com/images/bfdi-logo-370x370.png
79260
65370
https://fontmeme.com/images/disocery-family-font-370x370.png
22207
16191
https://fontmeme.com/images/gacha-life-font-x-370x370.jpg
46734
14214
https://fontmeme.com/images/plaints-trains-automobiles-font-1-370x559.jpg
46583
13919
https://fontmeme.com/images/grief-recovery-method-font-370x370.png
13251
10323
https://fontmeme.com/images/garnet-hill-logo-font-370x370.png
13019
10029
https://fontmeme.com/images/jackbox-games-logo-font-370x370.png
17224
9452
https://fontmeme.com/images/beastie-boys-story-font-370x555.jpg
39624
8670
https://fontmeme.com/images/kerrang-font-370x502.jpg
54459
8423
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 240 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Fontmeme.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://fontmeme.com/
0
https://fontmeme.com/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fontmeme.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 890 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://fontmeme.com/images/bfdi-logo-370x370.png
79836
https://fontmeme.com/images/tiger-king-font-370x548.jpg
64729
https://fontmeme.com/images/Todays-Golfer-UK-May-2020-typeface-370x523.jpg
60314
https://fontmeme.com/images/kerrang-font-370x502.jpg
55050
https://fontmeme.com/images/outer-banks-tv-1-370x548.jpg
47588
https://fontmeme.com/images/gacha-life-font-x-370x370.jpg
47324
https://fontmeme.com/images/plaints-trains-automobiles-font-1-370x559.jpg
47174
https://fontmeme.com/images/ahs-1984-font-370x556.jpg
44015
https://fontmeme.com/images/beastie-boys-story-font-370x555.jpg
40215
https://fontmeme.com/images/vast-of-night-poster-fm-370x548.jpg
39839
Uses efficient cache policy on static assets — 2 resources found
Fontmeme.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
19085
https://fontmeme.com/assets/style.css
3150000000
15495
Avoids an excessive DOM size — 293 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
293
Maximum DOM Depth
13
Maximum Child Elements
24
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fontmeme.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://fontmeme.com/
113.926
5.015
1.684
Unattributable
51.494
1.053
0.14
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
65.792
Other
63.953
Script Evaluation
37.053
Parse HTML & CSS
21.959
Rendering
13.516
Script Parsing & Compilation
6.915
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 — 32 requests • 890 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
32
911679
Image
27
851715
Font
1
20617
Script
1
19085
Stylesheet
1
15495
Document
1
4176
Other
1
591
Media
0
0
Third-party
2
19661
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)
19661
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
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.

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

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of fontmeme.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.
`[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.
`[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-*]` 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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

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.

Audio and video

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

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that fontmeme.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.

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.

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 Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
WordPress
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.

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
http://fontmeme.com/
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for fontmeme.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 fontmeme.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.
48

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

Fast and reliable

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

PWA Optimized

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 fontmeme.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.

Fast and reliable

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

Installable

Does not use HTTPS — 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
http://fontmeme.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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) 79
Performance 89
Accessibility 70
Best Practices 85
SEO 99
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://fontmeme.com/
Updated: 29th July, 2020

2.25 seconds
First Contentful Paint (FCP)
23%
63%
14%

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

Simulate loading on mobile
89

Performance

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

Metrics

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

Other

First CPU Idle — 1.4 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.4 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive fontmeme.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://fontmeme.com/
0
115.57799996808
580
0
301
text/html
https://fontmeme.com/
115.89200003073
334.56000010483
4176
23939
200
text/html
Document
https://fontmeme.com/global/fonts/oswald-v11-latin-ext_latin-regular.woff2
347.25499991328
368.39900002815
20617
20092
200
application/octet-stream
Font
https://fontmeme.com/assets/style.css
348.64400001243
377.39100004546
15495
69353
200
text/css
Stylesheet
https://fontmeme.com/assets/logo.png
369.55299996771
390.25599998422
7522
6933
200
image/png
Image
https://fontmeme.com/images/gacha-life-font-x-370x370.jpg
378.74300009571
398.97400001064
47324
46734
200
image/jpeg
Image
https://fontmeme.com/images/sekiro-shadows-die-twice-fontmeme-font-370x370.jpg
382.59000005201
412.08599996753
25609
25018
200
image/jpeg
Image
https://fontmeme.com/images/castle-crashers-font-370x370.jpg
382.81999994069
405.08299996145
36578
35987
200
image/jpeg
Image
https://fontmeme.com/images/Todays-Golfer-UK-May-2020-typeface-370x523.jpg
383.36999993771
408.45500002615
60314
59723
200
image/jpeg
Image
https://fontmeme.com/images/rough-and-rowdy-ways-font-370x370.jpg
383.49099992774
453.47899990156
23445
22854
200
image/jpeg
Image
https://fontmeme.com/images/bfdi-logo-370x370.png
383.59400001355
411.50799999014
79836
79260
200
image/png
Image
https://fontmeme.com/images/deltarune-game-font-370x370.jpg
384.97000001371
407.17800008133
23344
22753
200
image/jpeg
Image
https://fontmeme.com/images/vast-of-night-poster-fm-370x548.jpg
385.26799995452
457.67799997702
39839
39248
200
image/jpeg
Image
https://fontmeme.com/images/outer-banks-tv-1-370x548.jpg
385.4519999586
409.84000009485
47588
46997
200
image/jpeg
Image
https://fontmeme.com/images/tiger-king-font-370x548.jpg
385.6440000236
422.45299997739
64729
64138
200
image/jpeg
Image
https://fontmeme.com/images/mrs-america-font-370x463.jpg
385.74600010179
406.91799996421
24029
23438
200
image/jpeg
Image
https://fontmeme.com/images/beastie-boys-story-font-370x555.jpg
385.90100011788
410.59500002302
40215
39624
200
image/jpeg
Image
https://fontmeme.com/images/frighteners_movie_font-370x550.jpg
385.98000002094
411.21900011785
14741
14150
200
image/jpeg
Image
https://fontmeme.com/images/ahs-1984-font-370x556.jpg
386.04600005783
409.03900004923
44015
43424
200
image/jpeg
Image
https://fontmeme.com/images/grief-recovery-method-font-370x370.png
386.14600012079
407.40399993956
13841
13251
200
image/png
Image
https://fontmeme.com/images/Spoonflower-font-370x370.jpg
386.22500002384
407.68199996091
8250
7660
200
image/jpeg
Image
https://fontmeme.com/images/kerrang-font-370x502.jpg
386.29300007597
411.8300001137
55050
54459
200
image/jpeg
Image
https://fontmeme.com/images/garnet-hill-logo-font-370x370.png
386.36099989526
445.12999989092
13609
13019
200
image/png
Image
https://fontmeme.com/images/get-weird-deluxe-font-370x370.jpg
386.54200010933
412.45499998331
39478
38887
200
image/jpeg
Image
https://fontmeme.com/images/jackbox-games-logo-font-370x370.png
386.63000008091
410.33399989828
17814
17224
200
image/png
Image
https://fontmeme.com/images/HRB-logo-font-370x370.png
386.73599995673
410.08500009775
16216
15626
200
image/png
Image
https://fontmeme.com/images/disocery-family-font-370x370.png
386.86500000767
406.48499992676
22797
22207
200
image/png
Image
https://fontmeme.com/images/orange-box-font-370x469.jpg
386.93600008264
409.4140001107
37104
36513
200
image/jpeg
Image
https://fontmeme.com/images/plaints-trains-automobiles-font-1-370x559.jpg
387.01299997047
410.93900008127
47174
46583
200
image/jpeg
Image
https://www.google-analytics.com/analytics.js
387.08600006066
391.47999999113
19085
45958
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j83&a=2142614015&t=pageview&_s=1&dl=https%3A%2F%2Ffontmeme.com%2F&ul=en-us&de=UTF-8&dt=Font%20Meme%3A%20Fonts%20%26%20Typography%20Resource&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEAB~&jid=1613858225&gjid=166557485&cid=1225563467.1596012490&tid=UA-31486302-1&_gid=1232948510.1596012490&_r=1&z=1608187606
472.76800009422
478.14300004393
576
35
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
366.439
8.492
409.843
16.649
426.505
39.474
483.667
17.753
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 2790 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Properly size images
Images can slow down the page's load time. Fontmeme.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fontmeme.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fontmeme.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://fontmeme.com/assets/style.css
15495
2568
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fontmeme.com should consider minifying JS files.
Remove unused CSS — Potential savings of 13 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fontmeme.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://fontmeme.com/assets/style.css
15495
13790
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 220 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Fontmeme.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://fontmeme.com/
0
https://fontmeme.com/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fontmeme.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 890 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://fontmeme.com/images/bfdi-logo-370x370.png
79836
https://fontmeme.com/images/tiger-king-font-370x548.jpg
64729
https://fontmeme.com/images/Todays-Golfer-UK-May-2020-typeface-370x523.jpg
60314
https://fontmeme.com/images/kerrang-font-370x502.jpg
55050
https://fontmeme.com/images/outer-banks-tv-1-370x548.jpg
47588
https://fontmeme.com/images/gacha-life-font-x-370x370.jpg
47324
https://fontmeme.com/images/plaints-trains-automobiles-font-1-370x559.jpg
47174
https://fontmeme.com/images/ahs-1984-font-370x556.jpg
44015
https://fontmeme.com/images/beastie-boys-story-font-370x555.jpg
40215
https://fontmeme.com/images/vast-of-night-poster-fm-370x548.jpg
39839
Uses efficient cache policy on static assets — 2 resources found
Fontmeme.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
19085
https://fontmeme.com/assets/style.css
3150000000
15495
Avoids an excessive DOM size — 293 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
293
Maximum DOM Depth
13
Maximum Child Elements
24
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fontmeme.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.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://fontmeme.com/
295.012
10.632
4.284
Unattributable
93.676
3.42
1.072
https://www.google-analytics.com/analytics.js
74.008
63.932
5.604
Minimizes main-thread work — 0.5 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
180.532
Other
128.072
Script Evaluation
77.984
Parse HTML & CSS
40.324
Rendering
34.74
Script Parsing & Compilation
10.96
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 — 31 requests • 890 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
31
910990
Image
26
851037
Font
1
20617
Script
1
19085
Stylesheet
1
15495
Document
1
4176
Other
1
580
Media
0
0
Third-party
2
19661
Minimize third-party usage — Third-party code blocked the main thread for 10 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)
19661
9.996
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
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 — 2 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://fontmeme.com/
630
79
https://fontmeme.com/
1119
67

Budgets

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

Metrics

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

Opportunities

Eliminate render-blocking resources — Potential savings of 320 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fontmeme.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://fontmeme.com/assets/style.css
15495
330
Serve images in next-gen formats — Potential savings of 153 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://fontmeme.com/images/bfdi-logo-370x370.png
79260
65370
https://fontmeme.com/images/disocery-family-font-370x370.png
22207
16191
https://fontmeme.com/images/gacha-life-font-x-370x370.jpg
46734
14214
https://fontmeme.com/images/plaints-trains-automobiles-font-1-370x559.jpg
46583
13919
https://fontmeme.com/images/grief-recovery-method-font-370x370.png
13251
10323
https://fontmeme.com/images/garnet-hill-logo-font-370x370.png
13019
10029
https://fontmeme.com/images/jackbox-games-logo-font-370x370.png
17224
9452
https://fontmeme.com/images/beastie-boys-story-font-370x555.jpg
39624
8670
https://fontmeme.com/images/kerrang-font-370x502.jpg
54459
8423
70

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of fontmeme.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.
`[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.
`[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-*]` 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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

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.

Audio and video

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

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that fontmeme.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.

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.

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 Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
WordPress
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.

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
http://fontmeme.com/
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
99

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for fontmeme.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 fontmeme.com on mobile screens.
Document uses legible font sizes — 98.98% 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
html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video
1.02%
11.998px
98.98%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
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.

Mobile Friendly

Tap targets are not sized appropriately — 92% 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
4
26x25
5
26x25
3
26x25
63x32
73x32
80x32

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

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

Fast and reliable

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

PWA Optimized

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 fontmeme.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.

Fast and reliable

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

Installable

Does not use HTTPS — 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
http://fontmeme.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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: 104.26.2.12
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name: Whois Agent
Organization: Domain Protection Services, Inc.
Country: US
City: Denver
State: CO
Post Code: 80201
Email:
Phone: +1.7208009072
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Name.com, Inc. 104.18.7.161
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 4.1/5 (0 reviews)
WOT Trustworthiness: 82/100
WOT Child Safety: 94/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 16th July, 2020
Valid To: 16th July, 2021
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 4d04c09a
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 6008140493888608996007356333140618024
Serial Number (Hex): 0485203261176E0878FE27D004C22B28
Valid From: 16th July, 2024
Valid To: 16th July, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: 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 : Jul 16 01:10:31.209 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:8F:5D:04:C6:46:61:6D:EF:35:80:33:
C4:BE:EC:D5:44:51:F1:2D:86:1B:81:D8:46:01:01:94:
9B:F8:92:BD:C4:02:20:5E:B1:E4:F3:E1:6F:C0:D7:09:
1B:B0:4F:55:95:BC:91:AE:E0:CD:E7:C3:91:6F:24:4A:
BC:8E:40:82:49:96:40
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 : Jul 16 01:10:31.254 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:BB:2B:71:3F:6E:98:74:49:72:00:16:
A3:9E:66:51:76:40:38:B0:1A:3F:D5:1C:D3:51:FC:7A:
34:4A:80:1E:BB:02:20:71:4F:28:AA:05:56:41:5F:B3:
94:2F:B3:DE:57:CD:6A:C9:23:75:91:AA:EB:03:90:4D:
C6:0C:1C:2D:53:4C:42
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.fontmeme.com
DNS:sni.cloudflaressl.com
DNS:fontmeme.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 29th July, 2020
Content-Type: text/html; charset=UTF-8
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Expires: 29th October, 1923
Server: cloudflare
Connection: keep-alive
Set-Cookie: *
Last-Modified: 27th July, 2020
Vary: Accept-Encoding,User-Agent
Pragma: no-cache
CF-Cache-Status: DYNAMIC
cf-request-id: 043b5aca410000096f25b04200000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
CF-RAY: 5ba593f06a5f096f-IAD

Whois Lookup

Created: 3rd January, 2012
Changed: 16th February, 2020
Expires: 3rd January, 2026
Registrar: Name.com, Inc.
Status: clientTransferProhibited
Nameservers: dave.ns.cloudflare.com
lisa.ns.cloudflare.com
Owner Name: Whois Agent
Owner Organization: Domain Protection Services, Inc.
Owner Street: PO Box 1769
Owner Post Code: 80201
Owner City: Denver
Owner State: CO
Owner Country: US
Owner Phone: +1.7208009072
Owner Email: https://www.name.com/contact-domain-whois/fontmeme.com
Admin Name: Whois Agent
Admin Organization: Domain Protection Services, Inc.
Admin Street: PO Box 1769
Admin Post Code: 80201
Admin City: Denver
Admin State: CO
Admin Country: US
Admin Phone: +1.7208009072
Admin Email: https://www.name.com/contact-domain-whois/fontmeme.com
Tech Name: Whois Agent
Tech Organization: Domain Protection Services, Inc.
Tech Street: PO Box 1769
Tech Post Code: 80201
Tech City: Denver
Tech State: CO
Tech Country: US
Tech Phone: +1.7208009072
Tech Email: https://www.name.com/contact-domain-whois/fontmeme.com
Full Whois: Domain Name: FONTMEME.COM
Registry Domain ID: 1695112332_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.name.com
Registrar URL: http://www.name.com
Updated Date: 2020-02-16T05:27:01Z
Creation Date: 2012-01-03T08:06:27Z
Registrar Registration Expiration Date: 2026-01-03T08:06:27Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Reseller:
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Whois Agent
Registrant Organization: Domain Protection Services, Inc.
Registrant Street: PO Box 1769
Registrant City: Denver
Registrant State/Province: CO
Registrant Postal Code: 80201
Registrant Country: US
Registrant Phone: +1.7208009072
Registrant Fax: +1.7209758725
Registrant Email: https://www.name.com/contact-domain-whois/fontmeme.com
Registry Admin ID: Not Available From Registry
Admin Name: Whois Agent
Admin Organization: Domain Protection Services, Inc.
Admin Street: PO Box 1769
Admin City: Denver
Admin State/Province: CO
Admin Postal Code: 80201
Admin Country: US
Admin Phone: +1.7208009072
Admin Fax: +1.7209758725
Admin Email: https://www.name.com/contact-domain-whois/fontmeme.com
Registry Tech ID: Not Available From Registry
Tech Name: Whois Agent
Tech Organization: Domain Protection Services, Inc.
Tech Street: PO Box 1769
Tech City: Denver
Tech State/Province: CO
Tech Postal Code: 80201
Tech Country: US
Tech Phone: +1.7208009072
Tech Fax: +1.7209758725
Tech Email: https://www.name.com/contact-domain-whois/fontmeme.com
Name Server: lisa.ns.cloudflare.com
Name Server: dave.ns.cloudflare.com
DNSSEC: unSigned
Registrar Abuse Contact Email: abuse@name.com
Registrar Abuse Contact Phone: +1.7203101849
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2020-07-29T08:47:57Z <<<

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


The data in the Name.com, Inc. WHOIS database is provided by Name.com, Inc. for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Name.com, Inc. does not guarantee its accuracy. Users accessing the Name.com, Inc. WHOIS service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Name.com, Inc., except as reasonably necessary to register domain names or modify existing registrations. When using the Name.com, Inc. WHOIS service, please consider the following: the WHOIS service is not a replacement for standard EPP commands to the SRS service. WHOIS is not considered authoritative for registered domain objects. The WHOIS service may be scheduled for downtime during production or OT&E maintenance periods. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis, for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://www.name.com/layered-access-request . Name.com, Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.



Nameservers

Name IP Address
dave.ns.cloudflare.com 108.162.193.109
lisa.ns.cloudflare.com 108.162.192.131
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$703 USD 2/5
0/5