vegan.com

vegan.com is SSL secured

Free website and domain report on vegan.com

Last Updated: 25th February, 2021 Update Now
Overview

Snoop Summary for vegan.com

This is a free and comprehensive report about vegan.com. Vegan.com is hosted in North Charleston, South Carolina in United States on a server with an IP address of 104.196.179.149, where USD is the local currency and the local language is English. Our records indicate that vegan.com is owned/operated by Mocana Productions, Inc.. Vegan.com has the potential to be earning an estimated $6 USD per day from advertising revenue. If vegan.com was to be sold it would possibly be worth $4,431 USD (based on the daily revenue potential of the website over a 24 month period). Vegan.com receives an estimated 2,125 unique visitors every day - a large amount of traffic! This report was last updated 25th February, 2021.

About vegan.com

Site Preview: vegan.com vegan.com
Title: Vegan Made Easy - A healthy plant-based lifestyle - Vegan.com
Description: Vegan.com offers the web’s most extensive assortment of information about vegan lifestyles and plant-based eating. Zero fluff, clickbait, or intrusive ads.
Keywords and Tags: restaurants
Related Terms: ahoj brause pulver vegan, german vegan brands, is leonardo dicaprio vegan, is paul rudd vegan, paul rudd vegan, pretreatment plant, vegan food delivery, vegan frozen pizza, vegan meal delivery, vegan near me
Fav Icon:
Age: Over 26 years old
Domain Created: 22nd May, 1997
Domain Updated: 23rd April, 2020
Domain Expires: 23rd May, 2021
Review

Snoop Score

3/5 (Great!)

Valuation

$4,431 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 265,155
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: 2,125
Monthly Visitors: 64,682
Yearly Visitors: 775,670
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $6 USD
Monthly Revenue: $184 USD
Yearly Revenue: $2,211 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: vegan.com 9
Domain Name: vegan 5
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.91 seconds
Load Time Comparison: Faster than 83% of sites

PageSpeed Insights

Avg. (All Categories) 82
Performance 91
Accessibility 94
Best Practices 87
SEO 92
Progressive Web App 45
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://vegan.com/
Updated: 25th February, 2021

2.04 seconds
First Contentful Paint (FCP)
42%
48%
10%

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

Simulate loading on desktop
91

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for vegan.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.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 1.8 s
The time taken for the page to become fully interactive.
Total Blocking Time — 140 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.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.6 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 0.9 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 vegan.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://vegan.com/
http/1.1
0
19.054000003962
258
0
301
text/html
https://vegan.com/
http/1.1
19.698999996763
52.502000005916
20358
157092
200
text/html
Document
https://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
http/1.1
69.646000003559
129.91400000465
79624
661876
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Muli%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto+Slab%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic&ver=5.6.1&display=swap
http/1.1
70.049999994808
88.111000004574
3087
63984
200
text/css
Stylesheet
https://vegan.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
http/1.1
89.833999998518
98.31299999496
3147
7890
200
application/javascript
Script
https://z-na.amazon-adsystem.com/widgets/onejs?MarketPlace=US&adInstanceId=5ca8e63f-15eb-47b5-ae58-7635c5111419
http/1.1
99.78200000478
139.13199999661
7806
22370
200
application/javascript
Script
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
http/1.1
134.18100000126
183.75500000548
191674
739358
200
application/javascript
Script
https://vegan.com/wp-content/cache/busting/google-tracking/ga-6a10eb2bb5c90414980729f4f96ffbda.js
http/1.1
169.24499999732
180.06800000148
20045
47332
200
application/javascript
Script
data
178.60299999302
178.76199999591
0
67
200
image/svg+xml
Image
data
180.84800000361
180.90599999414
0
68
200
image/svg+xml
Image
data
182.44400000549
182.53299999924
0
64
200
image/svg+xml
Image
data
184.46699999913
184.53100000625
0
69
200
image/svg+xml
Image
data
186.55399999989
186.62300000142
0
68
200
image/svg+xml
Image
data
188.32200000179
188.38799999503
0
68
200
image/svg+xml
Image
data
190.24799999897
190.29600000067
0
68
200
image/svg+xml
Image
data
191.64499999897
191.68499999796
0
70
200
image/svg+xml
Image
data
193.78800000413
193.87899999856
0
68
200
image/svg+xml
Image
https://vegan.com/wp-content/uploads/2020/02/vegancom-opening-image.jpg
http/1.1
228.30299999623
234.21500000404
83206
82850
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2020/01/how-to-go-vegan-1.jpg
http/1.1
229.67400000198
239.23700000159
182234
181877
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2020/01/vegan-cooking-guide.jpg
http/1.1
235.12300000584
241.48799999966
172070
171713
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2019/08/easy-vegan-foods-carrot-soup-1.jpeg
http/1.1
240.13099999866
256.95900000574
78735
78379
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2019/06/vegan-guide-3.jpg
http/1.1
244.68099999649
250.42899999244
13938
13583
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2019/06/vegan-guide-4.jpg
http/1.1
245.19499999587
261.86400000006
13346
12991
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2019/01/pexels-photo-1446267.jpeg
http/1.1
250.93900000502
260.82199999655
70244
69888
200
image/jpeg
Image
https://fonts.gstatic.com/s/muli/v22/7Auwp_0qiz-afTLGLQjUwkQ.woff2
http/1.1
256.28800000413
259.21999999264
25453
24884
200
font/woff2
Font
https://vegan.com/wp-content/plugins/elementor/assets/lib/font-awesome/webfonts/fa-solid-900.woff2
http/1.1
256.71299999522
263.19199999853
80656
80300
200
font/woff2
Font
https://fonts.gstatic.com/s/muli/v22/7Au-p_0qiz-afTf2LwLT4EYFOA.woff2
http/1.1
257.57899999735
261.48499999545
26376
25808
200
font/woff2
Font
https://aax-us-east.amazon-adsystem.com/x/getad?src=330&c=100&sz=1x1&apiVersion=2.0&pj=%7B%22overwrite%22%3A%22false%22%2C%22div_name%22%3A%22amzn-assoc-ad-5ca8e63f-15eb-47b5-ae58-7635c5111419%22%2C%22tracking_id%22%3A%22vegancom%22%2C%22ad_type%22%3A%22one_tag%22%2C%22marketplace%22%3A%22amazon%22%2C%22enable_geo_redirection%22%3A%22true%22%2C%22enable_auto_tagging%22%3A%22false%22%2C%22region%22%3A%22US%22%2C%22placement%22%3A%22adunit%22%2C%22viewerCountry%22%3A%22US%22%2C%22textlinks%22%3A%22%22%2C%22debug%22%3A%22false%22%2C%22acap_publisherId%22%3A%22vegancom%22%2C%22slotNum%22%3A0%7D&u=https%3A%2F%2Fvegan.com%2F&jscb=amzn_assoc_jsonp_callback_adunit_0
http/1.1
387.14799999434
455.02900000429
381
50
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j88&a=1074840901&t=pageview&_s=1&dl=https%3A%2F%2Fvegan.com%2F&ul=en-us&de=UTF-8&dt=Vegan%20Made%20Easy%20-%20A%20healthy%20plant-based%20lifestyle%20-%20Vegan.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAAABAAAAAC~&jid=972038684&gjid=1579101775&cid=369069764.1614250527&tid=UA-726419-1&_gid=2002386793.1614250527&_r=1&_slc=1&z=535666662
http/1.1
591.40799999295
594.40499999619
618
2
200
text/plain
XHR
https://vegan.com/wp-content/uploads/2018/11/logo_vegancom_header.png.webp
http/1.1
596.1740000057
600.99399999308
2863
2510
200
image/webp
Image
https://vegan.com/wp-content/plugins/elementor/assets/lib/eicons/fonts/eicons.woff2?5.10.0
http/1.1
654.6079999971
660.4789999983
84864
84508
200
font/woff2
Font
https://fls-na.amazon-adsystem.com/1/action-impressions/1/OE/associates-adsystems/action/cm_:onejs_load_evt@v=381,onejs_exec_time@v=6,aax_load_time@v=685,aax_load_time_one_tag@v=685,aax_punt@v=1,aax_punt_one_tag@v=1?marketplace=US&service=AmazonWidgets&method=Widgets_Render_Time&marketplaceId=ATVPDKIKX0DER&requestId=758d303d-32a4-4380-9ed4-b90df6829d37&session=3e2de2ac-e032-4685-a47f-665771edae07
http/1.1
1072.0460000011
1128.5879999923
146
0
204
text/plain
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)
86.037
8.241
163.962
33.487
198.238
29.104
227.373
113.574
362.382
39.954
406.728
11.261
420.186
7.851
428.772
138.278
567.069
28.929
596.044
26.293
629.629
465.625
1108.644
6.364
1119.168
33.192
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Vegan.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Vegan.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Vegan.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Vegan.com should consider minifying JS files.
Remove unused CSS — Potential savings of 70 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Vegan.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://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
79624
71899
Remove unused JavaScript — Potential savings of 121 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://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
191674
124136
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 60 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://vegan.com/wp-content/uploads/2020/01/vegan-cooking-guide.jpg
171713
28407
https://vegan.com/wp-content/uploads/2020/01/how-to-go-vegan-1.jpg
181877
24621
https://vegan.com/wp-content/uploads/2019/01/pexels-photo-1446267.jpeg
69888
8834
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 30 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://vegan.com/
33.8
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Vegan.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://vegan.com/
190
https://vegan.com/
0
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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
48

Diagnostics

Avoids enormous network payloads — Total size was 1,134 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
191674
https://vegan.com/wp-content/uploads/2020/01/how-to-go-vegan-1.jpg
182234
https://vegan.com/wp-content/uploads/2020/01/vegan-cooking-guide.jpg
172070
https://vegan.com/wp-content/plugins/elementor/assets/lib/eicons/fonts/eicons.woff2?5.10.0
84864
https://vegan.com/wp-content/uploads/2020/02/vegancom-opening-image.jpg
83206
https://vegan.com/wp-content/plugins/elementor/assets/lib/font-awesome/webfonts/fa-solid-900.woff2
80656
https://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
79624
https://vegan.com/wp-content/uploads/2019/08/easy-vegan-foods-carrot-soup-1.jpeg
78735
https://vegan.com/wp-content/uploads/2019/01/pexels-photo-1446267.jpeg
70244
https://fonts.gstatic.com/s/muli/v22/7Au-p_0qiz-afTf2LwLT4EYFOA.woff2
26376
Uses efficient cache policy on static assets — 2 resources found
Vegan.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://aax-us-east.amazon-adsystem.com/x/getad?src=330&c=100&sz=1x1&apiVersion=2.0&pj=%7B%22overwrite%22%3A%22false%22%2C%22div_name%22%3A%22amzn-assoc-ad-5ca8e63f-15eb-47b5-ae58-7635c5111419%22%2C%22tracking_id%22%3A%22vegancom%22%2C%22ad_type%22%3A%22one_tag%22%2C%22marketplace%22%3A%22amazon%22%2C%22enable_geo_redirection%22%3A%22true%22%2C%22enable_auto_tagging%22%3A%22false%22%2C%22region%22%3A%22US%22%2C%22placement%22%3A%22adunit%22%2C%22viewerCountry%22%3A%22US%22%2C%22textlinks%22%3A%22%22%2C%22debug%22%3A%22false%22%2C%22acap_publisherId%22%3A%22vegancom%22%2C%22slotNum%22%3A0%7D&u=https%3A%2F%2Fvegan.com%2F&jscb=amzn_assoc_jsonp_callback_adunit_0
0
381
https://z-na.amazon-adsystem.com/widgets/onejs?MarketPlace=US&adInstanceId=5ca8e63f-15eb-47b5-ae58-7635c5111419
300000
7806
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Vegan.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.6 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://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
644.142
564.134
15.798
https://vegan.com/
264.929
19.399
1.82
Unattributable
58.184
1.325
0.184
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
624.883
Style & Layout
194.782
Other
94.48
Rendering
47.008
Parse HTML & CSS
43.28
Garbage Collection
25.323
Script Parsing & Compilation
22.758
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 — 23 requests • 1,134 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
23
1161129
Image
9
616782
Script
5
223053
Font
4
217349
Stylesheet
2
82711
Document
1
20358
Other
2
876
Media
0
0
Third-party
7
63867
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)
54916
0
8333
0
618
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
div
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.00038048633000613
0.00028044537839652
0.00012394684134489
0.00010280477482999
6.2930128710271E-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 — 3 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://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
1725
233
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
1560
138
https://vegan.com/
398
57
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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 — 1.6 s
The timing of the largest text or image that is painted.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 430 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Vegan.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://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
79624
190
https://fonts.googleapis.com/css?family=Muli%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto+Slab%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic&ver=5.6.1&display=swap
3087
230
Preload key requests — Potential savings of 430 ms
Key requests can be preloaded by using '<link rel=preload>'. Vegan.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://vegan.com/wp-content/plugins/elementor/assets/lib/font-awesome/webfonts/fa-solid-900.woff2
430
https://vegan.com/wp-content/plugins/elementor/assets/lib/eicons/fonts/eicons.woff2?5.10.0
390
Preload Largest Contentful Paint image — Potential savings of 430 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://vegan.com/wp-content/uploads/2020/02/vegancom-opening-image.jpg
430

Diagnostics

Avoid an excessive DOM size — 1,227 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
1227
Maximum DOM Depth
42
Maximum Child Elements
16

Diagnostics

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
94

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of vegan.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.
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.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Vegan.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that vegan.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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
jQuery UI
1.12.1
WordPress
core-js
core-js-pure@2.6.11; core-js-global@2.6.11; core-js-pure@2.6.11; core-js-global@2.6.11
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://vegan.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
92

SEO

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

Content Best Practices

Links do not have descriptive text — 8 links found
Make use of descriptive link text to assist search engines in understanding the content.

Manual Checks

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

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of vegan.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) 71
Performance 44
Accessibility 92
Best Practices 80
SEO 89
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://vegan.com/
Updated: 25th February, 2021

2.45 seconds
First Contentful Paint (FCP)
34%
54%
12%

0.03 seconds
First Input Delay (FID)
92%
7%
1%

Simulate loading on mobile
44

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for vegan.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

Opportunities

Properly size images
Images can slow down the page's load time. Vegan.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Vegan.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Vegan.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Vegan.com should consider minifying JS files.
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 20 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://vegan.com/
17.094
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Vegan.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://vegan.com/
630
https://vegan.com/
0
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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
48

Diagnostics

Avoids enormous network payloads — Total size was 1,079 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
191674
https://vegan.com/wp-content/uploads/2020/01/vegan-cooking-guide.jpg
172070
https://vegan.com/wp-content/uploads/2019/05/how-to-go-vegan.jpeg
139416
https://vegan.com/wp-content/plugins/elementor/assets/lib/eicons/fonts/eicons.woff2?5.10.0
84864
https://vegan.com/wp-content/uploads/2020/02/vegancom-opening-image.jpg
83206
https://vegan.com/wp-content/plugins/elementor/assets/lib/font-awesome/webfonts/fa-solid-900.woff2
80656
https://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
79624
https://vegan.com/wp-content/uploads/2019/08/easy-vegan-foods-carrot-soup-1.jpeg
78735
https://vegan.com/wp-content/uploads/2019/01/pexels-photo-1446267.jpeg
70244
https://fonts.gstatic.com/s/muli/v22/7Au-p_0qiz-afTf2LwLT4EYFOA.woff2
26376
Uses efficient cache policy on static assets — 2 resources found
Vegan.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://aax-us-east.amazon-adsystem.com/x/getad?src=330&c=100&sz=1x1&apiVersion=2.0&pj=%7B%22overwrite%22%3A%22false%22%2C%22div_name%22%3A%22amzn-assoc-ad-5ca8e63f-15eb-47b5-ae58-7635c5111419%22%2C%22tracking_id%22%3A%22vegancom%22%2C%22ad_type%22%3A%22one_tag%22%2C%22marketplace%22%3A%22amazon%22%2C%22enable_geo_redirection%22%3A%22true%22%2C%22enable_auto_tagging%22%3A%22false%22%2C%22region%22%3A%22US%22%2C%22placement%22%3A%22adunit%22%2C%22viewerCountry%22%3A%22US%22%2C%22textlinks%22%3A%22%22%2C%22debug%22%3A%22false%22%2C%22acap_publisherId%22%3A%22vegancom%22%2C%22slotNum%22%3A0%7D&u=https%3A%2F%2Fvegan.com%2F&jscb=amzn_assoc_jsonp_callback_adunit_0
0
381
https://z-na.amazon-adsystem.com/widgets/onejs?MarketPlace=US&adInstanceId=5ca8e63f-15eb-47b5-ae58-7635c5111419
300000
7814
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Vegan.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.
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 — 22 requests • 1,079 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
22
1104511
Image
8
560026
Script
5
223061
Font
4
217349
Stylesheet
2
82856
Document
1
20358
Other
2
861
Media
0
0
Third-party
7
64020
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)
55061
0
8341
0
618
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
div
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0014277140299479
0.00046230740017361
6.1204698350694E-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 — 6 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://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
7015
865
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
6390
512
https://vegan.com/
1312
207
https://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
2940
113
https://vegan.com/wp-content/cache/busting/google-tracking/ga-6a10eb2bb5c90414980729f4f96ffbda.js
6902
108
https://vegan.com/
1519
63
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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

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://vegan.com/
http/1.1
0
4.7600000398234
243
0
301
text/html
https://vegan.com/
http/1.1
5.4489999893121
21.5470000403
20358
157092
200
text/html
Document
https://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
http/1.1
39.789000002202
94.615000009071
79624
661876
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Muli%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto+Slab%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic&ver=5.6.1&display=swap
http/1.1
40.108999994118
57.614999997895
3232
70361
200
text/css
Stylesheet
https://vegan.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
http/1.1
60.235999990255
65.127999987453
3147
7890
200
application/javascript
Script
https://z-na.amazon-adsystem.com/widgets/onejs?MarketPlace=US&adInstanceId=5ca8e63f-15eb-47b5-ae58-7635c5111419
http/1.1
66.510999982711
88.333000021521
7814
22370
200
application/javascript
Script
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
http/1.1
89.946000021882
131.71799998963
191674
739358
200
application/javascript
Script
https://vegan.com/wp-content/cache/busting/google-tracking/ga-6a10eb2bb5c90414980729f4f96ffbda.js
http/1.1
126.88500003424
135.43299998855
20045
47332
200
application/javascript
Script
data
134.68399998965
134.74300003145
0
67
200
image/svg+xml
Image
data
135.95700002043
136.00500003668
0
68
200
image/svg+xml
Image
data
137.21800001804
137.28700001957
0
64
200
image/svg+xml
Image
data
138.39199999347
138.43900000211
0
69
200
image/svg+xml
Image
data
139.61499999277
139.66400001664
0
68
200
image/svg+xml
Image
data
140.58400003705
140.63099998748
0
68
200
image/svg+xml
Image
data
141.83199999388
141.87600003788
0
68
200
image/svg+xml
Image
data
143.08900001924
143.13500002027
0
70
200
image/svg+xml
Image
data
144.35700001195
144.40400002059
0
68
200
image/svg+xml
Image
https://vegan.com/wp-content/uploads/2020/02/vegancom-opening-image.jpg
http/1.1
170.0510000228
175.57700001635
83206
82850
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2019/05/how-to-go-vegan.jpeg
http/1.1
171.02700000396
177.63900000136
139416
139059
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2020/01/vegan-cooking-guide.jpg
http/1.1
174.56300003687
179.87400002312
172070
171713
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2019/08/easy-vegan-foods-carrot-soup-1.jpeg
http/1.1
179.2649999843
184.13400003919
78735
78379
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2019/06/vegan-guide-4.jpg
http/1.1
182.83900001552
186.83500000043
13346
12991
200
image/jpeg
Image
https://vegan.com/wp-content/uploads/2019/01/pexels-photo-1446267.jpeg
http/1.1
186.58700003289
192.67600000603
70244
69888
200
image/jpeg
Image
https://vegan.com/wp-content/plugins/elementor/assets/lib/eicons/fonts/eicons.woff2?5.10.0
http/1.1
192.16800003778
200.57700003963
84864
84508
200
font/woff2
Font
https://fonts.gstatic.com/s/muli/v22/7Auwp_0qiz-afTLGLQjUwkQ.woff2
http/1.1
192.4369999906
195.56200003717
25453
24884
200
font/woff2
Font
https://vegan.com/wp-content/plugins/elementor/assets/lib/font-awesome/webfonts/fa-solid-900.woff2
http/1.1
193.60100000631
199.51499998569
80656
80300
200
font/woff2
Font
https://fonts.gstatic.com/s/muli/v22/7Au-p_0qiz-afTf2LwLT4EYFOA.woff2
http/1.1
193.7930000131
196.5130000026
26376
25808
200
font/woff2
Font
https://aax-us-east.amazon-adsystem.com/x/getad?src=330&c=100&sz=1x1&apiVersion=2.0&pj=%7B%22overwrite%22%3A%22false%22%2C%22div_name%22%3A%22amzn-assoc-ad-5ca8e63f-15eb-47b5-ae58-7635c5111419%22%2C%22tracking_id%22%3A%22vegancom%22%2C%22ad_type%22%3A%22one_tag%22%2C%22marketplace%22%3A%22amazon%22%2C%22enable_geo_redirection%22%3A%22true%22%2C%22enable_auto_tagging%22%3A%22false%22%2C%22region%22%3A%22US%22%2C%22placement%22%3A%22adunit%22%2C%22viewerCountry%22%3A%22US%22%2C%22textlinks%22%3A%22%22%2C%22debug%22%3A%22false%22%2C%22acap_publisherId%22%3A%22vegancom%22%2C%22slotNum%22%3A0%7D&u=https%3A%2F%2Fvegan.com%2F&jscb=amzn_assoc_jsonp_callback_adunit_0
http/1.1
313.43799998285
389.5650000195
381
50
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j88&a=1779019145&t=pageview&_s=1&dl=https%3A%2F%2Fvegan.com%2F&ul=en-us&de=UTF-8&dt=Vegan%20Made%20Easy%20-%20A%20healthy%20plant-based%20lifestyle%20-%20Vegan.com&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAAABAAAAAC~&jid=562714088&gjid=482678446&cid=414850648.1614250550&tid=UA-726419-1&_gid=911028400.1614250550&_r=1&_slc=1&z=1009625787
http/1.1
511.78699999582
515.97800001036
618
2
200
text/plain
XHR
https://vegan.com/wp-content/uploads/2018/11/logo_vegancom_header.png.webp
http/1.1
513.90399999218
521.59399999073
2863
2510
200
image/webp
Image
https://fls-na.amazon-adsystem.com/1/action-impressions/1/OE/associates-adsystems/action/cm_:onejs_load_evt@v=308,onejs_exec_time@v=5,aax_load_time@v=641,aax_load_time_one_tag@v=641,aax_punt@v=1,aax_punt_one_tag@v=1?marketplace=US&service=AmazonWidgets&method=Widgets_Render_Time&marketplaceId=ATVPDKIKX0DER&requestId=cfe319c3-ab03-4711-b4f7-9f67e03d91c8&session=15de472a-661e-4421-ac1c-10cf6ff92476
http/1.1
953.95699999062
1010.9730000258
146
0
204
text/plain
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)
55.157
8.791
126.787
28.294
155.122
20.853
176.002
103.422
296.503
31.34
333.825
9.352
345.77
8.49
354.286
6.752
361.284
128.052
489.354
21.755
511.263
27.076
544.43
432.534
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

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

Opportunities

Remove unused CSS — Potential savings of 68 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Vegan.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://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
79624
69500
Remove unused JavaScript — Potential savings of 122 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://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
191674
124620
Serve images in next-gen formats — Potential savings of 36 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://vegan.com/wp-content/uploads/2020/01/vegan-cooking-guide.jpg
171713
28407
https://vegan.com/wp-content/uploads/2019/01/pexels-photo-1446267.jpeg
69888
8834

Diagnostics

Avoid an excessive DOM size — 1,227 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
1227
Maximum DOM Depth
42
Maximum Child Elements
16
Reduce JavaScript execution time — 2.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
2407.424
2121.964
62.52
https://vegan.com/
803.568
54.6
7.68
Unattributable
222.784
4.292
0.668
https://vegan.com/wp-content/cache/busting/google-tracking/ga-6a10eb2bb5c90414980729f4f96ffbda.js
113.896
100.668
6.552
https://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
113.176
0
0
Minimize main-thread work — 3.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2339.956
Style & Layout
608.432
Other
366.264
Parse HTML & CSS
152.472
Rendering
116.012
Script Parsing & Compilation
89.364
Garbage Collection
75.528

Metrics

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

Other

First CPU Idle — 6.7 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 870 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 4.0 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 360 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 vegan.com as laggy when the latency is higher than 0.05 seconds.
First Contentful Paint (3G) — 8235 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 2,530 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Vegan.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://vegan.com/wp-content/cache/min/1/d41355f3b7537bd21b0c4ee1484dbb00.css
79624
1080
https://fonts.googleapis.com/css?family=Muli%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto+Slab%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CRoboto%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic&ver=5.6.1&display=swap
3232
780
Preload key requests — Potential savings of 2,430 ms
Key requests can be preloaded by using '<link rel=preload>'. Vegan.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://vegan.com/wp-content/plugins/elementor/assets/lib/eicons/fonts/eicons.woff2?5.10.0
2430
https://vegan.com/wp-content/plugins/elementor/assets/lib/font-awesome/webfonts/fa-solid-900.woff2
2130
Preload Largest Contentful Paint image — Potential savings of 2,880 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://vegan.com/wp-content/uploads/2020/02/vegancom-opening-image.jpg
2880

Diagnostics

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
92

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of vegan.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.
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 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.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Vegan.com may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-hidden="true"]` elements contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
Failing Elements

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

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that vegan.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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
jQuery UI
1.12.1
WordPress
core-js
core-js-pure@2.6.11; core-js-global@2.6.11; core-js-pure@2.6.11; core-js-global@2.6.11
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://vegan.com/wp-content/uploads/2018/11/logo_vegancom_header.png.webp
160 x 38
239 x 57
320 x 76

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://vegan.com/wp-content/cache/min/1/316e62e43989e5bc544250995b4dba25.js
89

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for vegan.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 vegan.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
dd, dl, dt, li, ol, ul
0.00%
0px
100.00%
≥ 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.
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 — 59% 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
37x25
37x25
47x25
47x25
47x25
142x25
168x25
94x25
94x25
122x25
122x25
142x25
160x25
69x25
83x25
83x25
66x25
104x25
88x25
88x25
117x25
58x25
55x25
47x25
82x25
82x25
101x25
49x25
49x25
100x25

Content Best Practices

Links do not have descriptive text — 8 links found
Make use of descriptive link text to assist search engines in understanding the content.

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of vegan.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.
Hosting

Server Location

Server IP Address: 104.196.179.149
Continent: North America
Country: United States
United States Flag
Region: South Carolina
City: North Charleston
Longitude: -79.9746
Latitude: 32.8608
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

Private Registration: No
Name: Erik Marcus
Organization: Mocana Productions, Inc.
Country: US
City: Honolulu
State: HI
Post Code: 96836-0157
Email: erik@vegan.com
Phone: +1.4083570783
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NAMECHEAP INC 104.16.99.56
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 4/5 (2 reviews)
WOT Trustworthiness: 81/100
WOT Child Safety: 92/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

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

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 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 : Feb 16 06:46:11.420 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:7E:0F:1C:B0:36:B2:C9:C9:DB:2B:68:ED:
2C:6A:42:3F:64:BA:D8:48:9C:1D:BD:0A:84:8D:E9:34:
A8:31:78:04:02:21:00:A2:11:CA:F7:57:D7:85:AB:24:
58:39:4C:D2:CE:5B:9F:45:95:E3:25:40:02:39:74:49:
2D:6A:9C:94:59:C2:CA
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Feb 16 06:46:11.499 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:25:49:20:DA:5E:44:15:BD:38:CD:D6:42:
69:5A:F8:53:1C:C8:E3:DE:0E:92:BD:DD:69:2F:27:B4:
08:72:0D:A7:02:20:08:28:FB:AA:83:D8:A9:83:54:18:
4C:DC:3E:B8:1C:4A:02:A0:C0:DC:C1:B8:04:06:20:A9:
20:3E:01:65:EC:94
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:vegan.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 25th February, 2021
Content-Type: text/html; charset=UTF-8
Cache-Control: max-age=600, must-revalidate
Content-Length: 157092
Connection: keep-alive
Keep-Alive: timeout=20
Vary: Accept-Encoding,Cookie
Link: <https://vegan.com/>; rel=shortlink
X-Powered-By: WP Engine
X-Cacheable: SHORT
X-Cache: HIT
X-Cache-Group: normal
Accept-Ranges: bytes

Whois Lookup

Created: 22nd May, 1997
Changed: 23rd April, 2020
Expires: 23rd May, 2021
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
Nameservers: ines.ns.cloudflare.com
newt.ns.cloudflare.com
Owner Name: Redacted for Privacy Purposes
Owner Organization: Redacted for Privacy Purposes
Owner Street: Redacted for Privacy Purposes
Owner Post Code: Redacted for Privacy Purposes
Owner City: Redacted for Privacy Purposes
Owner State: FL
Owner Country: US
Owner Phone: Redacted for Privacy Purposes
Owner Email: Select Contact Domain Holder link at https://www.namecheap.com/domains/whois/result?domain=vegan.com
Admin Name: Redacted for Privacy Purposes
Admin Organization: Redacted for Privacy Purposes
Admin Street: Redacted for Privacy Purposes
Admin Post Code: Redacted for Privacy Purposes
Admin City: Redacted for Privacy Purposes
Admin State: Redacted for Privacy Purposes
Admin Country: Redacted for Privacy Purposes
Admin Phone: Redacted for Privacy Purposes
Admin Email: Select Contact Domain Holder link at https://www.namecheap.com/domains/whois/result?domain=vegan.com
Tech Name: Redacted for Privacy Purposes
Tech Organization: Redacted for Privacy Purposes
Tech Street: Redacted for Privacy Purposes
Tech Post Code: Redacted for Privacy Purposes
Tech City: Redacted for Privacy Purposes
Tech State: Redacted for Privacy Purposes
Tech Country: Redacted for Privacy Purposes
Tech Phone: Redacted for Privacy Purposes
Tech Email: Select Contact Domain Holder link at https://www.namecheap.com/domains/whois/result?domain=vegan.com
Full Whois: Domain name: vegan.com
Registry Domain ID: 356101_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2020-04-23T06:18:52.08Z
Creation Date: 1997-05-22T04:00:00.00Z
Registrar Registration Expiration Date: 2021-05-23T04:00:00.00Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Redacted for Privacy Purposes
Registrant Name: Redacted for Privacy Purposes
Registrant Organization: Redacted for Privacy Purposes
Registrant Street: Redacted for Privacy Purposes
Registrant City: Redacted for Privacy Purposes
Registrant State/Province: FL
Registrant Postal Code: Redacted for Privacy Purposes
Registrant Country: US
Registrant Phone: Redacted for Privacy Purposes
Registrant Phone Ext: Redacted for Privacy Purposes
Registrant Fax: Redacted for Privacy Purposes
Registrant Fax Ext: Redacted for Privacy Purposes
Registrant Email: Select Contact Domain Holder link at https://www.namecheap.com/domains/whois/result?domain=vegan.com
Registry Admin ID: Redacted for Privacy Purposes
Admin Name: Redacted for Privacy Purposes
Admin Organization: Redacted for Privacy Purposes
Admin Street: Redacted for Privacy Purposes
Admin City: Redacted for Privacy Purposes
Admin State/Province: Redacted for Privacy Purposes
Admin Postal Code: Redacted for Privacy Purposes
Admin Country: Redacted for Privacy Purposes
Admin Phone: Redacted for Privacy Purposes
Admin Phone Ext: Redacted for Privacy Purposes
Admin Fax: Redacted for Privacy Purposes
Admin Fax Ext: Redacted for Privacy Purposes
Admin Email: Select Contact Domain Holder link at https://www.namecheap.com/domains/whois/result?domain=vegan.com
Registry Tech ID: Redacted for Privacy Purposes
Tech Name: Redacted for Privacy Purposes
Tech Organization: Redacted for Privacy Purposes
Tech Street: Redacted for Privacy Purposes
Tech City: Redacted for Privacy Purposes
Tech State/Province: Redacted for Privacy Purposes
Tech Postal Code: Redacted for Privacy Purposes
Tech Country: Redacted for Privacy Purposes
Tech Phone: Redacted for Privacy Purposes
Tech Phone Ext: Redacted for Privacy Purposes
Tech Fax: Redacted for Privacy Purposes
Tech Fax Ext: Redacted for Privacy Purposes
Tech Email: Select Contact Domain Holder link at https://www.namecheap.com/domains/whois/result?domain=vegan.com
Name Server: ines.ns.cloudflare.com
Name Server: newt.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-02-24T12:55:22.90Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

Nameservers

Name IP Address
ines.ns.cloudflare.com 108.162.192.164
newt.ns.cloudflare.com 173.245.59.212
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
$2,692 USD 2/5
0/5
$2,488 USD 1/5
$990 USD 1/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$10 USD 1/5
0/5
$2,692 USD 2/5
$1,019 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5