Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

bee.events

BEE Events - Event Management Agency - York, Leeds, Harrogate

Page Load Speed

5.5 sec in total

First Response

185 ms

Resources Loaded

3.4 sec

Page Rendered

1.9 sec

bee.events screenshot

About Website

Click here to check amazing BEE content. Otherwise, check out these important facts you probably never knew about bee.events

BEE Events are a full service event management agency based in Yorkshire delivering inspiring experiences at exciting venues across the UK and internationally - making the ordinary, extraordinary!

Visit bee.events

Key Findings

We analyzed Bee.events page load time and found that the first response time was 185 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

bee.events performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value1,760 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.118

85/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

bee.events

185 ms

www.bee.events

206 ms

screen.732.css

255 ms

responsive.js

191 ms

banner.js

177 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 98% of them (57 requests) were addressed to the original Bee.events, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Bee.events.

Page Optimization Overview & Recommendations

Page size can be reduced by 683.5 kB (4%)

Content Size

16.0 MB

After Optimization

15.3 MB

In fact, the total size of Bee.events main page is 16.0 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. 65% of websites need less resources to load. Images take 15.9 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 89.5 kB

  • Original 98.3 kB
  • After minification 57.7 kB
  • After compression 8.8 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 40.6 kB, which is 41% 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 89.5 kB or 91% of the original size.

Image Optimization

-4%

Potential reduce by 590.1 kB

  • Original 15.9 MB
  • After minification 15.3 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. BEE images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 401 B

  • Original 6.5 kB
  • After minification 6.4 kB
  • After compression 6.1 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

-17%

Potential reduce by 3.4 kB

  • Original 19.7 kB
  • After minification 19.7 kB
  • After compression 16.3 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. Bee.events needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (9%)

Requests Now

56

After Optimization

51

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

Accessibility Review

bee.events accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

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

High

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

High

Links do not have a discernible name

Best Practices

bee.events best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

bee.events SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

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

Open Graph data is detected on the main page of BEE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: