Tools & Wizards About Us
bigtree.events screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

bigtree.events

Page Load Speed

3.9 sec in total

First Response

60 ms

Resources Loaded

2.6 sec

Page Rendered

1.3 sec

bigtree.events screenshot

About Website

Welcome to bigtree.events homepage info - get ready to check Bigtree best content right away, or after learning these important things about bigtree.events

Big Tree Events is a Top Event management Company in kochi, Kerala,we deliver professional event management solutions and outdoor advertising solutions

Visit bigtree.events

Key Findings

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

Performance Metrics

bigtree.events performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

bigtree.events

60 ms

www.bigtreeadv.com

62 ms

slider.css

4 ms

style.css

9 ms

modernizr.custom.86080.js

26 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Bigtree.events, 91% (29 requests) were made to Bigtreeadv.com and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Bigtreeadv.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 299.7 kB (12%)

Content Size

2.5 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bigtree.events 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. 75% 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 12.9 kB

  • Original 15.3 kB
  • After minification 9.1 kB
  • After compression 2.4 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 6.2 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 12.9 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 997 B

  • Original 2.1 MB
  • After minification 2.1 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. Bigtree images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 132.4 kB

  • Original 183.2 kB
  • After minification 157.4 kB
  • After compression 50.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 132.4 kB or 72% of the original size.

CSS Optimization

-84%

Potential reduce by 153.4 kB

  • Original 183.3 kB
  • After minification 166.1 kB
  • After compression 29.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. Bigtree.events needs all CSS files to be minified and compressed as it can save up to 153.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (33%)

Requests Now

24

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bigtree.events

bigtree.events

60 ms

www.bigtreeadv.com

www.bigtreeadv.com

62 ms

slider.css

slider.css

4 ms

style.css

style.css

9 ms

modernizr.custom.86080.js

modernizr.custom.86080.js

26 ms

bootstrap.min.css

bootstrap.min.css

22 ms

font-awesome.min.css

font-awesome.min.css

893 ms

lightslider.css

lightslider.css

1678 ms

jquery.min.js

jquery.min.js

1681 ms

lightslider.js

lightslider.js

22 ms

bootstrap.min.js

bootstrap.min.js

22 ms

bigtree-logo.png

bigtree-logo.png

50 ms

events.jpg

events.jpg

32 ms

fashion.jpg

fashion.jpg

44 ms

dmeets.jpg

dmeets.jpg

41 ms

exhibition.jpg

exhibition.jpg

44 ms

award.jpg

award.jpg

41 ms

wedding.jpg

wedding.jpg

44 ms

gtm.js

gtm.js

44 ms

pattern.png

pattern.png

37 ms

1.jpg

1.jpg

281 ms

2.jpg

2.jpg

224 ms

3.jpg

3.jpg

221 ms

4.jpg

4.jpg

226 ms

5.jpg

5.jpg

224 ms

6.jpg

6.jpg

221 ms

gtm.js

gtm.js

469 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

34 ms

handel-gothic.ttf

handel-gothic.ttf

31 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

32 ms

MTCORSVA.TTF

MTCORSVA.TTF

50 ms

controls.png

controls.png

106 ms

Accessibility Review

bigtree.events accessibility score

81

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

bigtree.events best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

bigtree.events SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bigtree.events can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Bigtree.events 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

bigtree.events

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