Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

Page Load Speed

18.2 sec in total

First Response

1.7 sec

Resources Loaded

14.2 sec

Page Rendered

2.2 sec

spon.me screenshot

About Website

Visit spon.me now to see the best up-to-date Spon content for Japan and also check out these interesting facts you probably never knew about spon.me

Visit spon.me

Key Findings

We analyzed Spon.me page load time and found that the first response time was 1.7 sec and then it took 16.5 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

spon.me performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

spon.me

1742 ms

styles.css

338 ms

twitter-feed.css

356 ms

css

28 ms

style.css

554 ms

Our browser made a total of 257 requests to load all elements on the main page. We found that 45% of them (116 requests) were addressed to the original Spon.me, 12% (31 requests) were made to Facebook.com and 12% (30 requests) were made to Cdn.api.b.hatena.ne.jp. The less responsive or slowest element that took the longest time to load (10.5 sec) relates to the external source Mediad2.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 494.6 kB (15%)

Content Size

3.3 MB

After Optimization

2.8 MB

In fact, the total size of Spon.me main page is 3.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 200.6 kB

  • Original 228.5 kB
  • After minification 213.3 kB
  • After compression 28.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 200.6 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 58.2 kB

  • Original 2.8 MB
  • After minification 2.7 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. Spon images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 196.6 kB

  • Original 308.4 kB
  • After minification 290.6 kB
  • After compression 111.7 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 196.6 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 39.2 kB

  • Original 47.7 kB
  • After minification 31.8 kB
  • After compression 8.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. Spon.me needs all CSS files to be minified and compressed as it can save up to 39.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (26%)

Requests Now

254

After Optimization

187

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

Accessibility Review

spon.me accessibility score

53

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

<frame> or <iframe> elements do not have a title

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

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

spon.me best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

spon.me SEO score

83

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

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

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spon.me can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Spon.me 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 Spon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: