Tools & Wizards About Us
ahyeahohyeah.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ahyeahohyeah.com

Page Load Speed

5.8 sec in total

First Response

911 ms

Resources Loaded

4.6 sec

Page Rendered

331 ms

ahyeahohyeah.com screenshot

About Website

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

Visit ahyeahohyeah.com

Key Findings

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

Performance Metrics

ahyeahohyeah.com performance score

0

Network Requests Diagram

ahyeahohyeah.com

911 ms

style.css

349 ms

_else.css

523 ms

style.css

360 ms

index.css

362 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 90% of them (60 requests) were addressed to the original Ahyeahohyeah.com, 4% (3 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ahyeahohyeah.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 686.9 kB (35%)

Content Size

2.0 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 16.7 kB

  • Original 21.4 kB
  • After minification 20.7 kB
  • After compression 4.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. 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 16.7 kB or 78% of the original size.

Image Optimization

-16%

Potential reduce by 216.0 kB

  • Original 1.4 MB
  • After minification 1.2 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, Ahyeahohyeah needs image optimization as it can save up to 216.0 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 150.9 kB

  • Original 209.3 kB
  • After minification 183.0 kB
  • After compression 58.4 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 150.9 kB or 72% of the original size.

CSS Optimization

-89%

Potential reduce by 303.4 kB

  • Original 342.5 kB
  • After minification 307.1 kB
  • After compression 39.2 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. Ahyeahohyeah.com needs all CSS files to be minified and compressed as it can save up to 303.4 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (64%)

Requests Now

66

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ahyeahohyeah.com

ahyeahohyeah.com

911 ms

style.css

style.css

349 ms

_else.css

_else.css

523 ms

style.css

style.css

360 ms

index.css

index.css

362 ms

script.js

script.js

572 ms

common.css

common.css

176 ms

pagelayout.css

pagelayout.css

360 ms

printlayout.css

printlayout.css

190 ms

blockskin.css

blockskin.css

1118 ms

wp_style.css

wp_style.css

684 ms

overwrite.css

overwrite.css

337 ms

style.css

style.css

358 ms

theme.css

theme.css

181 ms

_else.css

_else.css

181 ms

_else.css

_else.css

194 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

183 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

176 ms

head.load.min.js

head.load.min.js

182 ms

movie.js

movie.js

347 ms

parts.js

parts.js

351 ms

fx.js

fx.js

538 ms

override.js

override.js

540 ms

load.js

load.js

362 ms

_bk.png

_bk.png

360 ms

bk_200.png

bk_200.png

384 ms

ayoy_logo_fin.png

ayoy_logo_fin.png

184 ms

logo_time.png

logo_time.png

181 ms

sign.png

sign.png

184 ms

result.png

result.png

179 ms

sign.png

sign.png

350 ms

result.png

result.png

350 ms

sign.png

sign.png

360 ms

result.png

result.png

362 ms

sign.png

sign.png

521 ms

result.png

result.png

523 ms

sign.png

sign.png

537 ms

sign.png

sign.png

540 ms

83x83n838a815b839383v838783b83g81i2014-05-132013.42.4681j.png

83x83n838a815b839383v838783b83g81i2014-05-132013.42.4681j.png

1976 ms

8dc590v8fee95f1.png

8dc590v8fee95f1.png

952 ms

banner.png

banner.png

1041 ms

10409862_680019528746828_1236264866_n.jpg

10409862_680019528746828_1236264866_n.jpg

695 ms

widgets.js

widgets.js

35 ms

_area_header.css

_area_header.css

683 ms

_area_billboard.css

_area_billboard.css

687 ms

_area_main.css

_area_main.css

836 ms

_area_side_a.css

_area_side_a.css

862 ms

_area_side_b.css

_area_side_b.css

867 ms

_area_footer.css

_area_footer.css

1012 ms

_block_header.css

_block_header.css

1041 ms

_block_billboard.css

_block_billboard.css

1046 ms

_block_main.css

_block_main.css

1110 ms

_block_side_a.css

_block_side_a.css

1180 ms

_block_side_b.css

_block_side_b.css

1184 ms

_block_footer.css

_block_footer.css

1220 ms

1_bf3.gif

1_bf3.gif

1221 ms

bubble_bg.png

bubble_bg.png

1296 ms

bubble_balloon_cnr.png

bubble_balloon_cnr.png

1349 ms

bubble_balloon_h.png

bubble_balloon_h.png

1353 ms

bubble_balloon_v.png

bubble_balloon_v.png

1395 ms

bubble_balloon_bg.png

bubble_balloon_bg.png

1401 ms

like.php

like.php

129 ms

button.65b4bc8f0d6592fdc51d322b3f197660.js

button.65b4bc8f0d6592fdc51d322b3f197660.js

21 ms

tweet_button.64a917b4a230f163048902c783e1530f.ja.html

tweet_button.64a917b4a230f163048902c783e1530f.ja.html

12 ms

CiVxVZUu1dU.js

CiVxVZUu1dU.js

486 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

549 ms

jot

jot

92 ms

SEO Factors

ahyeahohyeah.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ahyeahohyeah.com 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), while the claimed language is Japanese. Our system also found out that Ahyeahohyeah.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

ahyeahohyeah.com

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