Access refuze.com. REFUZE.com – Refuze to live Average …

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

refuze.com

127 ms

refuze.com

1327 ms

ticketsBlock.css

53 ms

dashicons.min.css

107 ms

variables-skeleton.min.css

153 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 62% of them (76 requests) were addressed to the original Refuze.com, 32% (39 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Refuze.com.

Content Size

2.5 MB

After Optimization

2.1 MB

In fact, the total size of Refuze.com main page is 2.5 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. 80% 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 249.9 kB

Original 297.5 kB
After minification 294.4 kB
After compression 47.5 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 249.9 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 80.2 kB

Original 1.8 MB
After minification 1.7 MB

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. REFUZE images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.6 kB

Original 242.3 kB
After minification 241.7 kB
After compression 236.7 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.

CSS Optimization

-2%

Potential reduce by 2.0 kB

Original 127.9 kB
After minification 127.9 kB
After compression 126.0 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. Refuze.com has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

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

High

Image elements do not have [alt] attributes

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

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Refuze.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 Refuze.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.

Social Sharing Optimization

refuze.com

Open Graph description is not detected on the main page of REFUZE. 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

REFUZE.com – Refuze to live Average …

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

refuze.com

refuze.com

ticketsBlock.css

dashicons.min.css

variables-skeleton.min.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

refuze.com

refuze.com

ticketsBlock.css

dashicons.min.css

variables-skeleton.min.css

variables-full.min.css

common-skeleton.min.css

common-full.min.css

tickets.min.css

rsvp-v1.min.css

theme.css

slider-pro.min.css

woocommerce-layout.css

woocommerce.css

cookieblocker.min.css

frontend.css

rsvp.min.css

s2member-o.php

timeme.min.js

burst.min.js

jquery.min.js

jquery-migrate.min.js

hrf-script.js

Popup.js

PopupConfig.js

PopupBuilder.js

rsslider.js

jquery.blockUI.min.js

add-to-cart.min.js

js.cookie.min.js

woocommerce.min.js

countdown.js

form.js

frontend.js

et-divi-customizer-global.min.css

css

css

wc-blocks.css

css

style.css

js

underscore-before.js

underscore.min.js