Tools & Wizards About Us
slide.ly screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

slide.ly

Promo Video Maker | Create Quick Promotional Videos Online

Page Load Speed

596 ms in total

First Response

23 ms

Resources Loaded

231 ms

Page Rendered

342 ms

slide.ly screenshot

About Website

Welcome to slide.ly homepage info - get ready to check Slide best content for United States right away, or after learning these important things about slide.ly

Make a promo video in minutes with our Free Promo Video Maker. 1000's of high-quality templates, 15 million HD clips, royalty-free music and free storage!

Visit slide.ly

Key Findings

We analyzed Slide.ly page load time and found that the first response time was 23 ms and then it took 573 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

slide.ly performance score

0

Network Requests Diagram

slide.ly

23 ms

style.scss

37 ms

league-gothic.scss

41 ms

homepage.scss

45 ms

css

24 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Slide.ly, 58% (15 requests) were made to Ak01-cdn.slidely.com and 8% (2 requests) were made to Ak03-cdn.slidely.com. The less responsive or slowest element that took the longest time to load (77 ms) relates to the external source Ak01-cdn.slidely.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 296.2 kB (19%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Slide.ly 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. 40% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 42.2 kB

  • Original 54.3 kB
  • After minification 51.2 kB
  • After compression 12.1 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 42.2 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 47.1 kB

  • Original 1.2 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. Slide images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 98.5 kB

  • Original 146.8 kB
  • After minification 146.0 kB
  • After compression 48.3 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 98.5 kB or 67% of the original size.

CSS Optimization

-72%

Potential reduce by 108.5 kB

  • Original 150.3 kB
  • After minification 148.2 kB
  • After compression 41.8 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. Slide.ly needs all CSS files to be minified and compressed as it can save up to 108.5 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (40%)

Requests Now

25

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

slide.ly

slide.ly

23 ms

style.scss

style.scss

37 ms

league-gothic.scss

league-gothic.scss

41 ms

homepage.scss

homepage.scss

45 ms

css

css

24 ms

require.js

require.js

43 ms

pinit.js

pinit.js

7 ms

grey.gif

grey.gif

29 ms

support-button.png

support-button.png

22 ms

slidesong.png

slidesong.png

47 ms

main-page-header-background-v2.jpg

main-page-header-background-v2.jpg

34 ms

slidesong-x.png

slidesong-x.png

16 ms

video-cover.jpg

video-cover.jpg

15 ms

video-overlay.png

video-overlay.png

17 ms

apps-show.png

apps-show.png

77 ms

apps-collage.png

apps-collage.png

49 ms

apps-gallery.png

apps-gallery.png

64 ms

apps-mobile.png

apps-mobile.png

63 ms

section-views-background.jpg

section-views-background.jpg

62 ms

slidesong-homepage.png

slidesong-homepage.png

47 ms

handlebars.js

handlebars.js

55 ms

underscore.js

underscore.js

52 ms

jquery.min.js

jquery.min.js

37 ms

pinit_main.js

pinit_main.js

22 ms

jquery-ui.min.js

jquery-ui.min.js

39 ms

backbone.js

backbone.js

15 ms

SEO Factors

slide.ly SEO score

0

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 Slide.ly 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 Slide.ly 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

slide.ly

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