Tools & Wizards About Us
u2source.com screenshot

Report Summary

  • 0

    Performance

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

Page Load Speed

1.4 sec in total

First Response

260 ms

Resources Loaded

948 ms

Page Rendered

175 ms

u2source.com screenshot

About Website

Visit u2source.com now to see the best up-to-date U 2 Source content and also check out these interesting facts you probably never knew about u2source.com

Visit u2source.com

Key Findings

We analyzed U2source.com page load time and found that the first response time was 260 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

u2source.com performance score

0

Network Requests Diagram

u2source.com

260 ms

style.css

72 ms

jquery.main.js

111 ms

jquery.matchHeight.js

73 ms

bookmark_button.js

387 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 18% of them (6 requests) were addressed to the original U2source.com, 24% (8 requests) were made to Apis.google.com and 12% (4 requests) were made to D7x5nblzs94me.cloudfront.net. The less responsive or slowest element that took the longest time to load (387 ms) relates to the external source B.st-hatena.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 149.2 kB (42%)

Content Size

358.1 kB

After Optimization

209.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of U2source.com main page is 358.1 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. Javascripts take 158.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 14.9 kB

  • Original 20.7 kB
  • After minification 20.2 kB
  • After compression 5.7 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.9 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 3.6 kB

  • Original 151.9 kB
  • After minification 148.3 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. U 2 Source images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 109.4 kB

  • Original 158.9 kB
  • After minification 139.5 kB
  • After compression 49.5 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 109.4 kB or 69% of the original size.

CSS Optimization

-80%

Potential reduce by 21.2 kB

  • Original 26.6 kB
  • After minification 19.5 kB
  • After compression 5.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. U2source.com needs all CSS files to be minified and compressed as it can save up to 21.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (61%)

Requests Now

31

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

u2source.com

u2source.com

260 ms

style.css

style.css

72 ms

jquery.main.js

jquery.main.js

111 ms

jquery.matchHeight.js

jquery.matchHeight.js

73 ms

bookmark_button.js

bookmark_button.js

387 ms

line-button.js

line-button.js

351 ms

in.js

in.js

21 ms

platform.js

platform.js

99 ms

button-only@2x.png

button-only@2x.png

315 ms

bg.png

bg.png

69 ms

top_image.jpg

top_image.jpg

190 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

29 ms

fastbutton

fastbutton

66 ms

postmessageRelay

postmessageRelay

61 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

14 ms

secureAnonymousFramework

secureAnonymousFramework

100 ms

btn.js

btn.js

40 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

35 ms

rpc:shindig_random.js

rpc:shindig_random.js

42 ms

258 ms

button

button

15 ms

button.css

button.css

75 ms

shared.js

shared.js

95 ms

button.js

button.js

93 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

27 ms

sprite_connect_v14.png

sprite_connect_v14.png

24 ms

pocket_button.png

pocket_button.png

4 ms

82x20.png

82x20.png

173 ms

reset.css

reset.css

14 ms

entry-button.css

entry-button.css

14 ms

bbtn-l_v3.png

bbtn-l_v3.png

5 ms

Accessibility Review

u2source.com accessibility score

45

Accessibility Issues

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

u2source.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

u2source.com SEO score

100

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

    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 U2source.com 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 U2source.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

u2source.com

Open Graph description is not detected on the main page of U 2 Source. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: