Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

sursly.com

Sursly.com

Page Load Speed

12 sec in total

First Response

1.7 sec

Resources Loaded

9.5 sec

Page Rendered

814 ms

sursly.com screenshot

About Website

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

Freelance graphic and type designer in Ithaca, New York

Visit sursly.com

Key Findings

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

Performance Metrics

sursly.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.301

39/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

www.tylerfinck.com

1676 ms

www.tylerfinck.com

4087 ms

woocommerce-layout.css

189 ms

woocommerce.css

222 ms

name-your-price.css

161 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Sursly.com, 17% (10 requests) were made to I1.wp.com and 14% (8 requests) were made to I2.wp.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Tylerfinck.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.0 kB (24%)

Content Size

1.4 MB

After Optimization

1.0 MB

In fact, the total size of Sursly.com main page is 1.4 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 941.2 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 46.6 kB

  • Original 53.1 kB
  • After minification 52.7 kB
  • After compression 6.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 46.6 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 21.7 kB

  • Original 941.2 kB
  • After minification 919.4 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. Sursly images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 106.8 kB

  • Original 184.1 kB
  • After minification 180.0 kB
  • After compression 77.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 106.8 kB or 58% of the original size.

CSS Optimization

-84%

Potential reduce by 148.0 kB

  • Original 176.6 kB
  • After minification 160.3 kB
  • After compression 28.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. Sursly.com needs all CSS files to be minified and compressed as it can save up to 148.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (44%)

Requests Now

54

After Optimization

30

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

Accessibility Review

sursly.com accessibility score

77

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

sursly.com best practices score

83

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

SEO Factors

sursly.com SEO score

93

Search Engine Optimization Advices

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

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sursly.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Sursly.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

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