Tools & Wizards About Us
waddleup.com screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

waddleup.com

Home WaddleUp!

Page Load Speed

9.6 sec in total

First Response

578 ms

Resources Loaded

7.8 sec

Page Rendered

1.2 sec

waddleup.com screenshot

About Website

Welcome to waddleup.com homepage info - get ready to check Waddle Up best content right away, or after learning these important things about waddleup.com

Find sanctuary at WaddleUp!, a social hub full of penguins from all around the globe. Meet new friends, dres up your penguin, obtain new loot and play minigames.

Visit waddleup.com

Key Findings

We analyzed Waddleup.com page load time and found that the first response time was 578 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

waddleup.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value3.0 s

93/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.219

57/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

waddleup.com

578 ms

tomfoolery.js

551 ms

emoji.css

536 ms

bootstrap.css

522 ms

font-awesome.min.css

639 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 62% of them (56 requests) were addressed to the original Waddleup.com, 11% (10 requests) were made to Abs.twimg.com and 8% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Waddleup.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (73%)

Content Size

1.6 MB

After Optimization

417.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waddleup.com main page is 1.6 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. CSS take 763.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 48.4 kB

  • Original 65.6 kB
  • After minification 57.4 kB
  • After compression 17.2 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 8.2 kB, which is 13% 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 48.4 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 43 B

  • Original 64.7 kB
  • After minification 64.7 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. Waddle Up images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 438.9 kB

  • Original 673.5 kB
  • After minification 591.1 kB
  • After compression 234.6 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 438.9 kB or 65% of the original size.

CSS Optimization

-87%

Potential reduce by 661.9 kB

  • Original 763.3 kB
  • After minification 716.6 kB
  • After compression 101.4 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. Waddleup.com needs all CSS files to be minified and compressed as it can save up to 661.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (54%)

Requests Now

80

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

waddleup.com

waddleup.com

578 ms

tomfoolery.js

tomfoolery.js

551 ms

emoji.css

emoji.css

536 ms

bootstrap.css

bootstrap.css

522 ms

font-awesome.min.css

font-awesome.min.css

639 ms

owl.carousel.css

owl.carousel.css

514 ms

owl.theme.css

owl.theme.css

514 ms

owl.transitions.css

owl.transitions.css

946 ms

custom.css

custom.css

1155 ms

aos.css

aos.css

1152 ms

responsive.css

responsive.css

955 ms

datatables.css

datatables.css

967 ms

font-awesome.min.css

font-awesome.min.css

3252 ms

jquery-ui.min.css

jquery-ui.min.css

3255 ms

timepicker.css

timepicker.css

3256 ms

jquery-ui.min.js

jquery-ui.min.js

3254 ms

timepicker.js

timepicker.js

3266 ms

widgets.js

widgets.js

113 ms

email-decode.min.js

email-decode.min.js

1165 ms

jquery.min.js

jquery.min.js

73 ms

bootstrap.js

bootstrap.js

3253 ms

jquery.vide.js

jquery.vide.js

3253 ms

owl.carousel.js

owl.carousel.js

3257 ms

numscroller-1.0.js

numscroller-1.0.js

3254 ms

aos.js

aos.js

3254 ms

common.js

common.js

3255 ms

jquery-ui.css

jquery-ui.css

3256 ms

jquery-ui.min.js

jquery-ui.min.js

84 ms

jquery.bpopup.js

jquery.bpopup.js

84 ms

notify.min.js

notify.min.js

3255 ms

normalize.css

normalize.css

2111 ms

jquery.js

jquery.js

685 ms

1f468-200d-1f469-200d-1f467-200d-1f466.png

1f468-200d-1f469-200d-1f467-200d-1f466.png

103 ms

20170316-ypmp1E0h0LboL1TfOLqI

20170316-ypmp1E0h0LboL1TfOLqI

256 ms

waddleuptext.png

waddleuptext.png

890 ms

map.png

map.png

594 ms

penguinpassicon.png

penguinpassicon.png

501 ms

trophy.png

trophy.png

581 ms

customdbbig.png

customdbbig.png

541 ms

lootventory.png

lootventory.png

1046 ms

lootisland.png

lootisland.png

1457 ms

drops.png

drops.png

1033 ms

unlockitems2.PNG

unlockitems2.PNG

1044 ms

puffleicon.png

puffleicon.png

1067 ms

discord.webp

discord.webp

1308 ms

twitter.png

twitter.png

1419 ms

5039.png

5039.png

1431 ms

tickload.gif

tickload.gif

1977 ms

4794.png

4794.png

1577 ms

2021.png

2021.png

1729 ms

4404.png

4404.png

1824 ms

5371.png

5371.png

1849 ms

966.png

966.png

2016 ms

1f511.png

1f511.png

159 ms

1f3ae.png

1f3ae.png

160 ms

BurbankSmall-Medium.otf

BurbankSmall-Medium.otf

2156 ms

BurbankSmall-Light%20(1).otf

BurbankSmall-Light%20(1).otf

2332 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2509 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2474 ms

BurbankSmall-Black%20(2).otf

BurbankSmall-Black%20(2).otf

2572 ms

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

130 ms

settings

settings

229 ms

bg.gif

bg.gif

2134 ms

bg.jpg

bg.jpg

2331 ms

bg.jpeg

bg.jpeg

2502 ms

bg.png

bg.png

2560 ms

widget

widget

254 ms

moment~timeline~tweet.ae149926685a43cb146e35371430188e.js

moment~timeline~tweet.ae149926685a43cb146e35371430188e.js

18 ms

timeline.687eed636a16648c9f0b1f72d7fa68bd.js

timeline.687eed636a16648c9f0b1f72d7fa68bd.js

33 ms

profile

profile

230 ms

index.f7afda7848e99e6cf0ab.css

index.f7afda7848e99e6cf0ab.css

75 ms

5a61f8e3e63b7e93777f.js

5a61f8e3e63b7e93777f.js

171 ms

v7suM-e6

v7suM-e6

253 ms

1f384.png

1f384.png

123 ms

1f385.png

1f385.png

178 ms

1f983.png

1f983.png

180 ms

1f633.png

1f633.png

177 ms

1f440.png

1f440.png

180 ms

1f60e.png

1f60e.png

191 ms

1f383.png

1f383.png

202 ms

2b07.png

2b07.png

186 ms

2600.png

2600.png

186 ms

1f427.png

1f427.png

190 ms

timeline.32f7f89e2e680ebfe3f4cfefb27966ae.dark.ltr.css

timeline.32f7f89e2e680ebfe3f4cfefb27966ae.dark.ltr.css

145 ms

timeline.32f7f89e2e680ebfe3f4cfefb27966ae.dark.ltr.css

timeline.32f7f89e2e680ebfe3f4cfefb27966ae.dark.ltr.css

145 ms

WLIJP6DF_normal.jpg

WLIJP6DF_normal.jpg

39 ms

EJNGSNUWoAY1HrA

EJNGSNUWoAY1HrA

56 ms

syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css

syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css

37 ms

syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css

syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css

41 ms

jot.html

jot.html

14 ms

Accessibility Review

waddleup.com accessibility score

89

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

Best Practices

waddleup.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

waddleup.com SEO score

85

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

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

    EN

  • Encoding

    UTF-8

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

waddleup.com

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