Tools & Wizards About Us
sur.ly screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

sur.ly

Sur.ly: turn your outbound links into a website growth factor.

Page Load Speed

1.3 sec in total

First Response

45 ms

Resources Loaded

496 ms

Page Rendered

714 ms

sur.ly screenshot

About Website

Visit sur.ly now to see the best up-to-date Sur content for India and also check out these interesting facts you probably never knew about sur.ly

Sur.ly protects, informs and recaptures users after they follow the outbound links.

Visit sur.ly

Key Findings

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

Performance Metrics

sur.ly performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

sur.ly

45 ms

global.css

41 ms

jquery.min.js

58 ms

jquery.placeholder.js

51 ms

tools.js

50 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Sur.ly, 84% (31 requests) were made to Cdn.sur.ly and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (168 ms) relates to the external source Js-agent.newrelic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 237.8 kB (36%)

Content Size

663.5 kB

After Optimization

425.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sur.ly main page is 663.5 kB. 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 391.0 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 14.1 kB

  • Original 20.5 kB
  • After minification 19.6 kB
  • After compression 6.3 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 14.1 kB or 69% of the original size.

Image Optimization

-13%

Potential reduce by 50.1 kB

  • Original 391.0 kB
  • After minification 340.9 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, Sur needs image optimization as it can save up to 50.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 144.0 kB

  • Original 216.1 kB
  • After minification 212.4 kB
  • After compression 72.1 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 144.0 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 29.5 kB

  • Original 36.0 kB
  • After minification 30.6 kB
  • After compression 6.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. Sur.ly needs all CSS files to be minified and compressed as it can save up to 29.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (48%)

Requests Now

31

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sur.ly

sur.ly

45 ms

global.css

global.css

41 ms

jquery.min.js

jquery.min.js

58 ms

jquery.placeholder.js

jquery.placeholder.js

51 ms

tools.js

tools.js

50 ms

popup.js

popup.js

50 ms

jquery.cookie.js

jquery.cookie.js

50 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

52 ms

auth.js

auth.js

50 ms

reset.css

reset.css

14 ms

menu.css

menu.css

14 ms

proximanova-black.css

proximanova-black.css

15 ms

proximanova-extrabold.css

proximanova-extrabold.css

17 ms

proximanova-regular.css

proximanova-regular.css

17 ms

proximanova-semibold.css

proximanova-semibold.css

16 ms

proximanova-bold.css

proximanova-bold.css

15 ms

analytics.js

analytics.js

116 ms

watch.js

watch.js

96 ms

stat.php

stat.php

102 ms

index-header.png

index-header.png

54 ms

sprite.png

sprite.png

51 ms

hiw-001.png

hiw-001.png

57 ms

001.png

001.png

50 ms

002.png

002.png

52 ms

003.png

003.png

50 ms

004.png

004.png

53 ms

005.png

005.png

53 ms

006.png

006.png

55 ms

ti-001.jpg

ti-001.jpg

80 ms

platforms.png

platforms.png

61 ms

lt-001.png

lt-001.png

66 ms

proximanova-regular-webfont.woff

proximanova-regular-webfont.woff

66 ms

proximanova-extrabold-webfont.woff

proximanova-extrabold-webfont.woff

62 ms

proximanova-black-webfont.woff

proximanova-black-webfont.woff

90 ms

proximanova-semibold-webfont.woff

proximanova-semibold-webfont.woff

78 ms

collect

collect

17 ms

nr-918.min.js

nr-918.min.js

168 ms

Accessibility Review

sur.ly accessibility score

62

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sur.ly best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

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

sur.ly

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