Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

littlebees.org

Little Bees International Play School, NRI Layout, Akshaya Nagar, Varanasi, Banaswadi, Bangalore, WCC Road, Ramavarmapuram, Nagercoil | Preschool | Da...

Page Load Speed

12.9 sec in total

First Response

813 ms

Resources Loaded

11.6 sec

Page Rendered

487 ms

About Website

Visit littlebees.org now to see the best up-to-date Little Bees content and also check out these interesting facts you probably never knew about littlebees.org

Little Bees International Play School, NRI Layout, Akshaya Nagar, Varanasi, Banaswadi, Bangalore, WCC Road, Ramavarmapuram, Nagercoil

Visit littlebees.org

Key Findings

We analyzed Littlebees.org page load time and found that the first response time was 813 ms and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

littlebees.org performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value35.0 s

0/100

25%

SI (Speed Index)

Value23.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,910 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.375

28/100

15%

TTI (Time to Interactive)

Value35.7 s

0/100

10%

Network Requests Diagram

littlebees.org

813 ms

littlebees.org

1045 ms

css

37 ms

css

62 ms

js

104 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 68% of them (59 requests) were addressed to the original Littlebees.org, 11% (10 requests) were made to Fonts.gstatic.com and 10% (9 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Littlebees.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.5 MB (40%)

Content Size

8.9 MB

After Optimization

5.4 MB

In fact, the total size of Littlebees.org main page is 8.9 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. Javascripts take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 1.6 MB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 279.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. 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 1.6 MB or 85% of the original size.

Image Optimization

-13%

Potential reduce by 363.5 kB

  • Original 2.8 MB
  • After minification 2.4 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. Obviously, Little Bees needs image optimization as it can save up to 363.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-37%

Potential reduce by 1.6 MB

  • Original 4.3 MB
  • After minification 4.3 MB
  • After compression 2.7 MB

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 1.6 MB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (32%)

Requests Now

73

After Optimization

50

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

Accessibility Review

littlebees.org accessibility score

61

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

littlebees.org best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

littlebees.org SEO score

90

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    UTF-8

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

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