2.5 sec in total
121 ms
2 sec
449 ms
Click here to check amazing Forbidden Flowers content. Otherwise, check out these important facts you probably never knew about forbiddenflowers.com
A cannabis brand for the apologetically sexy, cheeky, and fully free-spirited. Premium cannabis.
Visit forbiddenflowers.comWe analyzed Forbiddenflowers.com page load time and found that the first response time was 121 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
forbiddenflowers.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value5.1 s
24/100
25%
Value13.3 s
2/100
10%
Value2,170 ms
6/100
30%
Value0.07
96/100
15%
Value27.2 s
0/100
10%
121 ms
294 ms
70 ms
39 ms
43 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 63% of them (72 requests) were addressed to the original Forbiddenflowers.com, 15% (17 requests) were made to Aproperhigh.com and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (909 ms) belongs to the original domain Forbiddenflowers.com.
Page size can be reduced by 657.6 kB (10%)
6.8 MB
6.1 MB
In fact, the total size of Forbiddenflowers.com main page is 6.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.0 MB which makes up the majority of the site volume.
Potential reduce by 161.2 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 161.2 kB or 78% of the original size.
Potential reduce by 449.3 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Forbidden Flowers images are well optimized though.
Potential reduce by 43.3 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 3.9 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Forbiddenflowers.com has all CSS files already compressed.
Number of requests can be reduced by 71 (66%)
108
37
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forbidden Flowers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
forbiddenflowers.com
121 ms
forbiddenflowers.com
294 ms
gtm.js
70 ms
css2
39 ms
aos.css
43 ms
connect.js
284 ms
sbi-styles.min.css
254 ms
style.min.css
283 ms
styles.css
253 ms
style.css
35 ms
dittyDisplays.css
281 ms
all.css
52 ms
ffmain.min.css
60 ms
owl.carousel.min.css
61 ms
style.css
282 ms
et-divi-builder-dynamic-6.css
78 ms
jquery.min.js
99 ms
jquery-migrate.min.js
105 ms
owl.carousel.js
133 ms
klaviyo.js
22 ms
embed.js
75 ms
aos.js
14 ms
basic.min.css
104 ms
theme-ie11.min.css
144 ms
theme.min.css
147 ms
swiped-events.min.js
164 ms
imagesloaded.min.js
204 ms
effect.min.js
207 ms
ditty-news-ticker.js
459 ms
ffmain.min.js
508 ms
frontend.min.js
300 ms
scripts.min.js
673 ms
common.js
578 ms
wp-polyfill-inert.min.js
299 ms
regenerator-runtime.min.js
300 ms
wp-polyfill.min.js
301 ms
dom-ready.min.js
300 ms
hooks.min.js
303 ms
i18n.min.js
302 ms
a11y.min.js
305 ms
jquery.json.min.js
351 ms
gravityforms.min.js
351 ms
placeholders.jquery.min.js
360 ms
sbi-scripts.min.js
456 ms
custom.script.min.js
455 ms
js
52 ms
analytics.js
21 ms
collect
43 ms
js
37 ms
js
64 ms
connect_v5.1-plain.js
135 ms
fender_analytics.739eafc699de20b4c3bb.js
70 ms
static.047f24ade89e4aff54a9.js
78 ms
runtime.242037525aa1c76dfe9b.js
19 ms
sharedUtils.a2ead10f1141521a8e3e.js
20 ms
sbi-sprite.png
355 ms
Entrance-Modal-Desktop-1.jpeg
574 ms
desktop_accent.png
172 ms
Vector-1.png
197 ms
FFAgeGate.jpg
216 ms
age-gate-logo.png
217 ms
ff_logo.png
288 ms
FF_logo_mobile.png
570 ms
EffX.png
287 ms
hypeHome.png
288 ms
Card-Hype-Up.svg
288 ms
chill_home.png
303 ms
Card-Chill-Out.svg
569 ms
turnHome.png
321 ms
Card-Turn-On.svg
338 ms
zoneHome.png
353 ms
Card-Zone-In.svg
364 ms
home_rose1.png
369 ms
home_rose2.png
376 ms
tickerSticker.png
429 ms
placeholder.png
429 ms
twitter-icon.png
601 ms
facebook-icon.png
428 ms
12pt.png
428 ms
FF-Hero-2.png
430 ms
FF-Hero-Mobile.png
428 ms
home-section3.png
520 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqqFA.ttf
23 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDppqqFA.ttf
86 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2qFA.ttf
111 ms
I_urMpiDvgLdLh0fAtoftig.ttf
138 ms
emailbg2.png
909 ms
app.js
163 ms
prev.svg
17 ms
next.svg
332 ms
336336386_1147178849282303_3834256260243890306_nfull.jpg
390 ms
334558571_694191415823914_5208253557551962312_nfull.jpg
355 ms
333354014_224261609981504_2607083347978526975_nfull.jpg
344 ms
332314399_875917547045648_6094221006133136607_nfull.jpg
300 ms
connect_ping
72 ms
css2
13 ms
mapbox-gl.css
21 ms
js
91 ms
entry.03077199.css
101 ms
Search.d2e83cd5.css
16 ms
Geopicker.cf3364fb.css
17 ms
Primary.98fc0028.css
17 ms
CarouselWrapper.9ff0df09.css
16 ms
StoreCard.4c456d61.css
18 ms
entry.dd83f040.js
45 ms
default.3aa18580.js
61 ms
connect_ping.46feb8f9.js
13 ms
notification-bar-close-x.93aa19b1.svg
3 ms
mobile-nav-hamburger.68f545c1.svg
4 ms
close-x.d34dea94.svg
5 ms
proper-nav-logo.5b581dc1.svg
37 ms
search.f3842a90.svg
6 ms
twitter-icon.9524c0d3.svg
28 ms
instagram-icon.6fecbb4d.svg
95 ms
forbiddenflowers.com accessibility score
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.
Impact
Issue
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
Impact
Issue
ARIA IDs are not unique
forbiddenflowers.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
forbiddenflowers.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forbiddenflowers.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Forbiddenflowers.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
forbiddenflowers.com
Open Graph data is detected on the main page of Forbidden Flowers. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: