Tools & Wizards About Us
aafter.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

aafter.com

Free* Statistics Homework Help

Page Load Speed

1 sec in total

First Response

101 ms

Resources Loaded

840 ms

Page Rendered

107 ms

aafter.com screenshot

About Website

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

TeddyCanSearch | TeddyCanShop | TeddyCanPay | TeddyCanPlay | TeddyCanVote | TeddyCan Tutor | Tools for Bloggers & Fundraising

Visit aafter.com

Key Findings

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

Performance Metrics

aafter.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value1.045

2/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

aafter.com

101 ms

teddycan.com

126 ms

bootstrap_test3.css

74 ms

deepwebstyle.css

70 ms

jquery.min.js

143 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Aafter.com, 49% (19 requests) were made to Teddycan.com and 23% (9 requests) were made to Fun.teddycan.com. The less responsive or slowest element that took the longest time to load (366 ms) relates to the external source Fun.teddycan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 374.3 kB (20%)

Content Size

1.9 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aafter.com main page is 1.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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 32.8 kB

  • Original 42.4 kB
  • After minification 39.9 kB
  • After compression 9.6 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 32.8 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 16.3 kB

  • Original 1.4 MB
  • After minification 1.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. Aafter images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 175.9 kB

  • Original 249.8 kB
  • After minification 224.3 kB
  • After compression 73.9 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 175.9 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 149.3 kB

  • Original 180.9 kB
  • After minification 142.8 kB
  • After compression 31.6 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. Aafter.com needs all CSS files to be minified and compressed as it can save up to 149.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (53%)

Requests Now

36

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aafter.com

aafter.com

101 ms

teddycan.com

teddycan.com

126 ms

bootstrap_test3.css

bootstrap_test3.css

74 ms

deepwebstyle.css

deepwebstyle.css

70 ms

jquery.min.js

jquery.min.js

143 ms

search_style_test3.css

search_style_test3.css

71 ms

jquery.mixitup.min.js

jquery.mixitup.min.js

71 ms

yahoo-dom-event.js

yahoo-dom-event.js

6 ms

connection-min.js

connection-min.js

8 ms

animation-min.js

animation-min.js

9 ms

datasource-min.js

datasource-min.js

9 ms

autocomplete-min.js

autocomplete-min.js

21 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

70 ms

magnific-popup.css

magnific-popup.css

101 ms

jquery-ui.css

jquery-ui.css

6 ms

jquery-1.10.2.js

jquery-1.10.2.js

12 ms

jquery-ui.js

jquery-ui.js

15 ms

responsive-nav.js

responsive-nav.js

101 ms

move-top.js

move-top.js

101 ms

easing.js

easing.js

102 ms

angular.min.js

angular.min.js

40 ms

bootstrap.js

bootstrap.js

118 ms

shop-n-search.png

shop-n-search.png

132 ms

help-section.png

help-section.png

51 ms

arrow-top.png

arrow-top.png

35 ms

nav_icon.png

nav_icon.png

36 ms

1024x522_bg_5.jpg

1024x522_bg_5.jpg

36 ms

teddycan-logo1-teddy.png

teddycan-logo1-teddy.png

175 ms

top_move.png

top_move.png

37 ms

share-button.png

share-button.png

71 ms

homework-help-button.png

homework-help-button.png

72 ms

ng2.jpg

ng2.jpg

249 ms

ng8.jpg

ng8.jpg

290 ms

bag3.jpg

bag3.jpg

366 ms

bag1.jpg

bag1.jpg

346 ms

shoe2.jpg

shoe2.jpg

284 ms

wshoe1.jpg

wshoe1.jpg

134 ms

piwik.js

piwik.js

30 ms

404.htm

404.htm

39 ms

Accessibility Review

aafter.com accessibility score

82

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

aafter.com best practices score

42

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

aafter.com SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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

aafter.com

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