Tools & Wizards About Us
saintaside.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

saintaside.com

Saint Aside | News & Blog

Page Load Speed

4.7 sec in total

First Response

736 ms

Resources Loaded

3.6 sec

Page Rendered

272 ms

saintaside.com screenshot

About Website

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

Official website of the alternative rock band Saint Aside with news, dates, photos, videos and shop

Visit saintaside.com

Key Findings

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

Performance Metrics

saintaside.com performance score

0

Network Requests Diagram

en

736 ms

template.css

203 ms

style.css

234 ms

mootools.js

352 ms

caption.js

248 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 63% of them (41 requests) were addressed to the original Saintaside.com, 15% (10 requests) were made to Static.xx.fbcdn.net and 11% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (766 ms) belongs to the original domain Saintaside.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 494.9 kB (44%)

Content Size

1.1 MB

After Optimization

638.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saintaside.com main page is 1.1 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. 35% of websites need less resources to load. Images take 518.3 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 53.4 kB

  • Original 74.9 kB
  • After minification 69.0 kB
  • After compression 21.5 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 53.4 kB or 71% of the original size.

Image Optimization

-17%

Potential reduce by 89.3 kB

  • Original 518.3 kB
  • After minification 429.0 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. Obviously, Saint Aside needs image optimization as it can save up to 89.3 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 315.5 kB

  • Original 495.5 kB
  • After minification 494.6 kB
  • After compression 180.0 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 315.5 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 36.8 kB

  • Original 44.2 kB
  • After minification 28.2 kB
  • After compression 7.5 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. Saintaside.com needs all CSS files to be minified and compressed as it can save up to 36.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (39%)

Requests Now

64

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saint Aside. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

en

en

736 ms

template.css

template.css

203 ms

style.css

style.css

234 ms

mootools.js

mootools.js

352 ms

caption.js

caption.js

248 ms

addthis_widget.js

addthis_widget.js

12 ms

undo.css

undo.css

109 ms

layout.css

layout.css

110 ms

navi.css

navi.css

139 ms

content-layouts.css

content-layouts.css

158 ms

forms.css

forms.css

211 ms

fonts.css

fonts.css

213 ms

bg.jpg

bg.jpg

224 ms

de.png

de.png

131 ms

us_gb.png

us_gb.png

131 ms

SaintAsideAt55ArtsClub2012_xkl.jpg

SaintAsideAt55ArtsClub2012_xkl.jpg

338 ms

albumteaser_1_en_postrelease.jpg

albumteaser_1_en_postrelease.jpg

342 ms

teaser_player.jpg

teaser_player.jpg

235 ms

Albumteaser_sidebar_1_EN_postrelease.jpg

Albumteaser_sidebar_1_EN_postrelease.jpg

331 ms

Singleteaser_sidebar_1_EN_postrelease.jpg

Singleteaser_sidebar_1_EN_postrelease.jpg

334 ms

Shopteaser_sidebar_1_EN.jpg

Shopteaser_sidebar_1_EN.jpg

441 ms

facebook.png

facebook.png

343 ms

lastfm.png

lastfm.png

438 ms

myspace.png

myspace.png

442 ms

youtube.png

youtube.png

442 ms

twitter.png

twitter.png

448 ms

Way_out_of_Line.png

Way_out_of_Line.png

449 ms

AugMedia.png

AugMedia.png

553 ms

container_bg.jpg

container_bg.jpg

548 ms

container_head.jpg

container_head.jpg

756 ms

logo.png

logo.png

547 ms

boxes_main_top.png

boxes_main_top.png

548 ms

boxes_main_left.png

boxes_main_left.png

551 ms

boxes_main_right.png

boxes_main_right.png

645 ms

stripe_heading.png

stripe_heading.png

657 ms

boxes_bg.png

boxes_bg.png

657 ms

minus-small-circle.png

minus-small-circle.png

658 ms

jc_blog.gif

jc_blog.gif

678 ms

boxes_main_bot.png

boxes_main_bot.png

750 ms

boxes_side_top.png

boxes_side_top.png

766 ms

boxes_side_bot.png

boxes_side_bot.png

763 ms

footer_edge_top.jpg

footer_edge_top.jpg

741 ms

ga.js

ga.js

29 ms

300lo.json

300lo.json

44 ms

328.06187d0eee7bbd449e76.js

328.06187d0eee7bbd449e76.js

6 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

46 ms

__utm.gif

__utm.gif

31 ms

likebox.php

likebox.php

403 ms

McLpmVM3wCm.css

McLpmVM3wCm.css

287 ms

VH4VPudaxfN.css

VH4VPudaxfN.css

357 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

491 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

621 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

489 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

489 ms

217811_10151014213976691_108267672_n.jpg

217811_10151014213976691_108267672_n.jpg

437 ms

395371_10150456939421691_1606924468_n.jpg

395371_10150456939421691_1606924468_n.jpg

574 ms

12742626_617767771711702_3912884516902103828_n.jpg

12742626_617767771711702_3912884516902103828_n.jpg

698 ms

12734241_159428154439281_7428627912278558942_n.jpg

12734241_159428154439281_7428627912278558942_n.jpg

678 ms

10407714_1402582590037079_8146702952959063017_n.jpg

10407714_1402582590037079_8146702952959063017_n.jpg

640 ms

12032269_957922020947138_1856120889511798245_n.jpg

12032269_957922020947138_1856120889511798245_n.jpg

720 ms

12510368_1557027341289542_5735644261040701517_n.jpg

12510368_1557027341289542_5735644261040701517_n.jpg

663 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

73 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

72 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

69 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

70 ms

SEO Factors

saintaside.com SEO score

0

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

saintaside.com

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