Focl.com Site Title

FOCL - Premium CBD and plant-based wellness solutions

Focl.com Meta Description

FOCL brings you the right dose of wellness through premium CBD enhanced with adaptogens and botanicals. Vegan, gluten free, non GMO!

Focl.com Test Results

Focl.com Mobile Performance: 27/100
Quick overview:
Max Potential First Input Delay
1,050 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.
Time to Interactive
28.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.
First Meaningful Paint
5.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Enable text compression
Potential savings of 24 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.
Minify JavaScript
Potential savings of 32 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Avoid an excessive DOM size
1,481 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Properly size images
Potential savings of 190 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce unused JavaScript
Potential savings of 619 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce JavaScript execution time
13.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Eliminate render-blocking resources
Potential savings of 240 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Minimize main-thread work
27.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Largest Contentful Paint element
28,010 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce the impact of third-party code
Third-party code blocked the main thread for 6,070 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Serve static assets with an efficient cache policy
40 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Avoid enormous network payloads
Total size was 3,737 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Reduce unused CSS
Potential savings of 30 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 37 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Defer offscreen images
Potential savings of 66 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.

Focl.com Mobile SEO: 100/100
Quick overview:

Focl.com Mobile Best Practices: 59/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
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.
Focl.com Mobile Accessibility: 100/100
Quick overview:
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Similar sites
Similar tests
www.focl.com
www.focl.net
www.focl.org
www.focl.info
www.focl.biz
www.focl.us
www.focl.mobi
www.ocl.com
www.focl.com
www.cocl.com
www.fcocl.com
www.cfocl.com
www.docl.com
www.fdocl.com
www.dfocl.com
www.rocl.com
www.frocl.com
www.rfocl.com
www.tocl.com
www.ftocl.com
www.tfocl.com
www.gocl.com
www.fgocl.com
www.gfocl.com
www.vocl.com
www.fvocl.com
www.vfocl.com
www.fcl.com
www.ficl.com
www.foicl.com
www.fiocl.com
www.fkcl.com
www.fokcl.com
www.fkocl.com
www.flcl.com
www.folcl.com
www.flocl.com
www.fpcl.com
www.fopcl.com
www.fpocl.com
www.fol.com
www.foxl.com
www.focxl.com
www.foxcl.com
www.fodl.com
www.focdl.com
www.fodcl.com
www.fofl.com
www.focfl.com
www.fofcl.com
www.fovl.com
www.focvl.com
www.fovcl.com
www.foc.com
www.focp.com
www.foclp.com
www.focpl.com
www.foco.com
www.foclo.com
www.focol.com
www.fock.com
www.foclk.com
www.fockl.com
www.focl.con
Last Tested: