Tools & Wizards About Us
whally.com screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

whally.com

Your School's Best Friend | Whally

Page Load Speed

1.9 sec in total

First Response

83 ms

Resources Loaded

1.1 sec

Page Rendered

669 ms

whally.com screenshot

About Website

Welcome to whally.com homepage info - get ready to check Whally best content for United Kingdom right away, or after learning these important things about whally.com

Whally helps educators manage great schools and childcare centers

Visit whally.com

Key Findings

We analyzed Whally.com page load time and found that the first response time was 83 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

whally.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.178

68/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

whally.com

83 ms

whally.com

112 ms

511a24beba7f70d9fc47f2109037f1a8544292b5.css

50 ms

22d6fe5390d5ef251c3eac313196e6a3f0d330ca.js

180 ms

font-awesome.min.css

30 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 79% of them (22 requests) were addressed to the original Whally.com, 14% (4 requests) were made to Maxcdn.bootstrapcdn.com and 4% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (468 ms) relates to the external source Cdn.segment.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.3 kB (25%)

Content Size

256.5 kB

After Optimization

191.2 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Whally.com main page is 256.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 178.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 21.4 kB

  • Original 27.3 kB
  • After minification 17.5 kB
  • After compression 5.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 9.8 kB, which is 36% 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 21.4 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 4.3 kB

  • Original 178.0 kB
  • After minification 173.8 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. Whally images are well optimized though.

CSS Optimization

-77%

Potential reduce by 39.5 kB

  • Original 51.2 kB
  • After minification 51.2 kB
  • After compression 11.7 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. Whally.com needs all CSS files to be minified and compressed as it can save up to 39.5 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (14%)

Requests Now

21

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whally.com

whally.com

83 ms

whally.com

whally.com

112 ms

511a24beba7f70d9fc47f2109037f1a8544292b5.css

511a24beba7f70d9fc47f2109037f1a8544292b5.css

50 ms

22d6fe5390d5ef251c3eac313196e6a3f0d330ca.js

22d6fe5390d5ef251c3eac313196e6a3f0d330ca.js

180 ms

font-awesome.min.css

font-awesome.min.css

30 ms

css

css

81 ms

font-awesome.min.css

font-awesome.min.css

22 ms

analytics.min.js

analytics.min.js

468 ms

chart-img.jpg

chart-img.jpg

131 ms

proxima_nova_light-webfont.woff

proxima_nova_light-webfont.woff

74 ms

chart-img-2.jpg

chart-img-2.jpg

81 ms

whale-img.png

whale-img.png

92 ms

footer-logo.png

footer-logo.png

95 ms

info

info

79 ms

logo.png

logo.png

81 ms

title-blue.png

title-blue.png

81 ms

title-pink.png

title-pink.png

70 ms

ico-top-scores.png

ico-top-scores.png

71 ms

ico-game-overlap.png

ico-game-overlap.png

82 ms

ico-actionable-insights.png

ico-actionable-insights.png

86 ms

ico-granularity.png

ico-granularity.png

88 ms

ico-whale.png

ico-whale.png

99 ms

ico-privacy.png

ico-privacy.png

107 ms

proxima_nova_reg-webfont.woff

proxima_nova_reg-webfont.woff

124 ms

proxima_nova_bold-webfont.woff

proxima_nova_bold-webfont.woff

99 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

4 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

17 ms

_timesync

_timesync

19 ms

Accessibility Review

whally.com accessibility score

100

Accessibility Issues

Best Practices

whally.com 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

SEO Factors

whally.com SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

whally.com

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