Access excessively.net. Excessively - Cannabis legalization, made Excessively simpler

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value1,060 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

excessively.net

230 ms

www.excessively.net

495 ms

css

23 ms

common.css

95 ms

grid.css

85 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 75% of them (99 requests) were addressed to the original Excessively.net, 4% (5 requests) were made to Pagead2.googlesyndication.com and 4% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (495 ms) belongs to the original domain Excessively.net.

Content Size

1.3 MB

After Optimization

1.0 MB

In fact, the total size of Excessively.net main page is 1.3 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. 60% of websites need less resources to load. Images take 952.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 50.9 kB

Original 60.9 kB
After minification 51.7 kB
After compression 10.0 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. This page needs HTML code to be minified as it can gain 9.2 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.9 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 48.3 kB

Original 952.6 kB
After minification 904.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. Excessively images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 158.0 kB

Original 243.8 kB
After minification 222.0 kB
After compression 85.8 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 158.0 kB or 65% of the original size.

CSS Optimization

-80%

Potential reduce by 56.7 kB

Original 70.6 kB
After minification 67.7 kB
After compression 13.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. Excessively.net needs all CSS files to be minified and compressed as it can save up to 56.7 kB or 80% of the original size.

Requests Now

129

After Optimization

The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Excessively. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Excessively.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Excessively.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

excessively.net

Open Graph description is not detected on the main page of Excessively. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

Report Summary

Performance

Accessibility

Best Practices

SEO

Excessively - Cannabis legalization, made Excessively simpler

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

excessively.net

www.excessively.net

css

common.css

grid.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

excessively.net

www.excessively.net

css

common.css

grid.css

style.css

style-responsive.css

modernizr.js

script.js

show_ads.js

12589.js

jsapi

ca-pub-7563135538633152.js

zrt_lookup.html

show_ads_impl.js

ga.js

jquery.min.js

jquery.superfish.js

jquery-ui.js

jquery-ui.selectmenu.js

jquery.flexslider-min.js

jquery.quicksand.js

jquery.script.js

bg_body_1.jpg

bg_black_75.png

logo.png

bg_main_menu.png

main_slider_item.png

main_slider_01.jpg

main_slider_02.jpg

main_slider_03.jpg

main_slider_04.jpg

main_slider_05.jpg

main_slider_06.jpg

main_slider_07.jpg

main_slider_08.jpg

tabs_separator.png

main_tabs_01.jpg

main_tabs_02.jpg

main_tabs_03.jpg

main_tabs_04.jpg

main_tabs_05.jpg

main_tabs_21.jpg