Tools & Wizards About Us
striking.ly screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

striking.ly

How To Make a Website – Free Website Builder | Strikingly

Page Load Speed

3 sec in total

First Response

325 ms

Resources Loaded

2.2 sec

Page Rendered

540 ms

striking.ly screenshot

About Website

Click here to check amazing Striking content. Otherwise, check out these important facts you probably never knew about striking.ly

Strikingly is the best free website builder for anyone to create a gorgeous, mobile-friendly website easily. Quick, simple and stylish. Make your own free website today.

Visit striking.ly

Key Findings

We analyzed Striking.ly page load time and found that the first response time was 325 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

striking.ly performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.161

73/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

www.strikingly.com

325 ms

www.strikingly.com

1108 ms

landing-new-11c8c04d63376ecdadf264075c269d65.css

67 ms

css

82 ms

1113608435.js

130 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Striking.ly, 7% (2 requests) were made to Strikingly.com and 4% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Strikingly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 867.1 kB (79%)

Content Size

1.1 MB

After Optimization

233.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Striking.ly 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. Javascripts take 851.7 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 29.7 kB

  • Original 42.7 kB
  • After minification 42.7 kB
  • After compression 13.0 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 29.7 kB or 70% of the original size.

Image Optimization

-4%

Potential reduce by 915 B

  • Original 25.7 kB
  • After minification 24.8 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. Striking images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 681.5 kB

  • Original 851.7 kB
  • After minification 648.2 kB
  • After compression 170.2 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 681.5 kB or 80% of the original size.

CSS Optimization

-86%

Potential reduce by 155.0 kB

  • Original 180.1 kB
  • After minification 180.1 kB
  • After compression 25.1 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. Striking.ly needs all CSS files to be minified and compressed as it can save up to 155.0 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

12

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Striking. According to our analytics all requests are already optimized.

Network Requests Diagram

www.strikingly.com

www.strikingly.com

325 ms

www.strikingly.com

www.strikingly.com

1108 ms

landing-new-11c8c04d63376ecdadf264075c269d65.css

landing-new-11c8c04d63376ecdadf264075c269d65.css

67 ms

css

css

82 ms

1113608435.js

1113608435.js

130 ms

landing-8ad65ff46575b84ca8cebf41308a28d5.js

landing-8ad65ff46575b84ca8cebf41308a28d5.js

20 ms

OpenSans-Regular-webfont-303037f29b6bb058b4e7b2b4c9d58091.woff

OpenSans-Regular-webfont-303037f29b6bb058b4e7b2b4c9d58091.woff

127 ms

OpenSans-Light-webfont-6779c40cc7c3df8b18895770c439ff20.woff

OpenSans-Light-webfont-6779c40cc7c3df8b18895770c439ff20.woff

149 ms

OpenSans-Semibold-webfont-6302fe41985cabecf9ad3cf5cd41faa2.woff

OpenSans-Semibold-webfont-6302fe41985cabecf9ad3cf5cd41faa2.woff

150 ms

OpenSans-Bold-webfont-96485a496ddd1ca8c2bec0c1144c1767.woff

OpenSans-Bold-webfont-96485a496ddd1ca8c2bec0c1144c1767.woff

149 ms

analytics.min.js

analytics.min.js

561 ms

blank-100ca22768aa63e0d4e97eb7f5f4bc75.png

blank-100ca22768aa63e0d4e97eb7f5f4bc75.png

160 ms

seth-godin-f4352f50b2de590d1042c3109bb996cf.jpg

seth-godin-f4352f50b2de590d1042c3109bb996cf.jpg

160 ms

rebecca-bloom-601013b6133fb3ec20e337399e24028b.jpg

rebecca-bloom-601013b6133fb3ec20e337399e24028b.jpg

161 ms

mike-pacifico-79772e259a7835a0a8a9c34c4de436cb.jpg

mike-pacifico-79772e259a7835a0a8a9c34c4de436cb.jpg

159 ms

zia-kusuma-fc9db3fe47fac09f23af2f4a230aded1.jpg

zia-kusuma-fc9db3fe47fac09f23af2f4a230aded1.jpg

170 ms

big-arrow-left-100933969911630a17340c40ff8804b1.png

big-arrow-left-100933969911630a17340c40ff8804b1.png

171 ms

big-arrow-right-f280ffd3513d20afeec8ff19f12e52f1.png

big-arrow-right-f280ffd3513d20afeec8ff19f12e52f1.png

169 ms

brandon_reg-webfont-03fec3d75471e394d08c1621b5f7dc22.woff

brandon_reg-webfont-03fec3d75471e394d08c1621b5f7dc22.woff

122 ms

brandon_light-webfont-0dd9e481832af747cdf2a5c16b4badc3.woff

brandon_light-webfont-0dd9e481832af747cdf2a5c16b4badc3.woff

119 ms

brandon_med-webfont-46038c42a3811ea38608c14800e60f4e.woff

brandon_med-webfont-46038c42a3811ea38608c14800e60f4e.woff

121 ms

brandon_bld-webfont-1ad3dfb19911e61250c5ba0185000042.woff

brandon_bld-webfont-1ad3dfb19911e61250c5ba0185000042.woff

147 ms

entypo-fontello-dba1590e878a3cbdcdd63150d0e8acac.woff

entypo-fontello-dba1590e878a3cbdcdd63150d0e8acac.woff

144 ms

OpenSans-Italic-webfont-986113d956a869816a4c643f417adb7e.woff

OpenSans-Italic-webfont-986113d956a869816a4c643f417adb7e.woff

147 ms

OpenSans-LightItalic-webfont-09f0cc35ee7ea0e2a203ffff3e9c8571.woff

OpenSans-LightItalic-webfont-09f0cc35ee7ea0e2a203ffff3e9c8571.woff

145 ms

OpenSans-SemiboldItalic-webfont-7edacaf5b933396d24f247a503ec3385.woff

OpenSans-SemiboldItalic-webfont-7edacaf5b933396d24f247a503ec3385.woff

145 ms

OpenSans-BoldItalic-webfont-ce3a206c5c5851d7078cc37295ce6b9d.woff

OpenSans-BoldItalic-webfont-ce3a206c5c5851d7078cc37295ce6b9d.woff

144 ms

Accessibility Review

striking.ly accessibility score

71

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

striking.ly SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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

striking.ly

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