Tools & Wizards About Us
someone.io screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    81% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

someone.io

Upwave - Upwave

Page Load Speed

1.3 sec in total

First Response

200 ms

Resources Loaded

957 ms

Page Rendered

105 ms

someone.io screenshot

About Website

Welcome to someone.io homepage info - get ready to check Someone best content for Norway right away, or after learning these important things about someone.io

Visit someone.io

Key Findings

We analyzed Someone.io page load time and found that the first response time was 200 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

someone.io performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

www.someone.io

200 ms

default.css

93 ms

doa1hwd.js

159 ms

www.someone.io

187 ms

1kpw4g3QTqedYSM3dTi2WBDALtlnvkx3nPMjrV-ZAl9ffOeREN32IgCjMKM2HMItgX4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

28 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 22% of them (2 requests) were addressed to the original Someone.io, 67% (6 requests) were made to Use.typekit.net and 11% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (200 ms) belongs to the original domain Someone.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 kB (57%)

Content Size

2.3 kB

After Optimization

984 B

  • HTML

In fact, the total size of Someone.io main page is 2.3 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. 15% of websites need less resources to load. HTML takes 2.3 kB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 1.3 kB

  • Original 2.3 kB
  • After minification 2.0 kB
  • After compression 984 B

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. This page needs HTML code to be minified as it can gain 277 B, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.3 kB or 57% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.someone.io

www.someone.io

200 ms

default.css

default.css

93 ms

doa1hwd.js

doa1hwd.js

159 ms

www.someone.io

www.someone.io

187 ms

1kpw4g3QTqedYSM3dTi2WBDALtlnvkx3nPMjrV-ZAl9ffOeREN32IgCjMKM2HMItgX4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

1kpw4g3QTqedYSM3dTi2WBDALtlnvkx3nPMjrV-ZAl9ffOeREN32IgCjMKM2HMItgX4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

28 ms

3J9BVdikgg1hEq527XoJLnVvMs33wlH6Rb3nKnxc-PCffOcREN32IgCjMKM2HMItgI4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

3J9BVdikgg1hEq527XoJLnVvMs33wlH6Rb3nKnxc-PCffOcREN32IgCjMKM2HMItgI4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

53 ms

_i3EFwtMf4CLbpRnoayv5eiUnm1aqlBO7fs3j2LIg0JffO7REN32IgCjMKM2HMIt2q4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

_i3EFwtMf4CLbpRnoayv5eiUnm1aqlBO7fs3j2LIg0JffO7REN32IgCjMKM2HMIt2q4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

80 ms

AsIU2pxa0YGnk9ywy_oqNgUxezIk2sENafIXSeDnnAjffOHREN32IgCjMKM2HMItI94MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

AsIU2pxa0YGnk9ywy_oqNgUxezIk2sENafIXSeDnnAjffOHREN32IgCjMKM2HMItI94MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

108 ms

p.gif

p.gif

122 ms

Accessibility Review

someone.io accessibility score

95

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

Links do not have a discernible name

Best Practices

someone.io 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

someone.io SEO score

89

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

High

Tap targets are not sized appropriately

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 Someone.io 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 Someone.io 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

someone.io

Open Graph description is not detected on the main page of Someone. 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: