Herb.co Site Title

Weed Dispensaries, Strains, Culture & News | Herb

Herb.co Meta Description

Herb is the go-to destination for weed discovery, dispensaries, strains, education, culture and community for cannabis and marijuana enthusiasts around the globe.

Herb.co Test Results

Herb.co Mobile Performance: 33/100
Quick overview:
Time to Interactive
29.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
790 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
First Meaningful Paint
4.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Server Backend Latencies
590 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Script Treemap Data
Used for treemap app
Resources Summary
Aggregates all network requests and groups them by type
Metrics
Collects all available metrics.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Network Requests
Lists the network requests that were made during page load.
Final Screenshot
The last screenshot captured of the pageload.

45658973568

Diagnostics
Collection of useful page vitals.
Network Round Trip Times
250 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.

Herb.co Mobile SEO: 91/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn how to make pages mobile-friendly.
Tap targets are not sized appropriately
82% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

Herb.co Mobile Best Practices: 78/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Herb.co Mobile PWA: 88/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.
Herb.co Mobile Accessibility: 77/100
Quick overview:
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Navigation
These are opportunities to improve keyboard navigation in your application.
`[id]` attributes on active, focusable elements are not unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn how to fix duplicate `id`s.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Similar sites
Similar tests
www.herb.com
www.herb.net
www.herb.org
www.herb.info
www.herb.biz
www.herb.us
www.herb.mobi
www.erb.co
www.herb.co
www.berb.co
www.hberb.co
www.bherb.co
www.gerb.co
www.hgerb.co
www.gherb.co
www.yerb.co
www.hyerb.co
www.yherb.co
www.uerb.co
www.huerb.co
www.uherb.co
www.jerb.co
www.hjerb.co
www.jherb.co
www.nerb.co
www.hnerb.co
www.nherb.co
www.hrb.co
www.hwrb.co
www.hewrb.co
www.hwerb.co
www.hsrb.co
www.hesrb.co
www.hserb.co
www.hdrb.co
www.hedrb.co
www.hderb.co
www.hrrb.co
www.herrb.co
www.hrerb.co
www.heb.co
www.heeb.co
www.hereb.co
www.heerb.co
www.hedb.co
www.herdb.co
www.hefb.co
www.herfb.co
www.hefrb.co
www.hetb.co
www.hertb.co
www.hetrb.co
www.her.co
www.herv.co
www.herbv.co
www.hervb.co
www.herg.co
www.herbg.co
www.hergb.co
www.herh.co
www.herbh.co
www.herhb.co
www.hern.co
www.herbn.co
www.hernb.co
Last Tested: