Tools & Wizards About Us

Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

unpossible.co

Netfirms | This site is temporarily unavailable

Page Load Speed

620 ms in total

First Response

105 ms

Resources Loaded

425 ms

Page Rendered

90 ms

About Website

Click here to check amazing Unpossible content. Otherwise, check out these important facts you probably never knew about unpossible.co

Small business web hosting offering additional business services such as: domain name registrations, email accounts, web services, FrontPage help, online community resources and various small business...

Visit unpossible.co

Key Findings

We analyzed Unpossible.co page load time and found that the first response time was 105 ms and then it took 515 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

unpossible.co performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

unpossible.co

105 ms

generic_csscomponent.css

176 ms

rekicker.css

159 ms

87ae207201c55b84c5270851159260e1.1

158 ms

hd-h1-logo.png

136 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 9% of them (1 request) were addressed to the original Unpossible.co, 45% (5 requests) were made to Secure.netfirms.com and 45% (5 requests) were made to Www2.netfirms.com. The less responsive or slowest element that took the longest time to load (176 ms) relates to the external source Www2.netfirms.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.5 kB (39%)

Content Size

50.2 kB

After Optimization

30.7 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Unpossible.co main page is 50.2 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. Only 10% of websites need less resources to load. CSS take 28.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 6.8 kB

  • Original 8.7 kB
  • After minification 6.3 kB
  • After compression 1.9 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. This page needs HTML code to be minified as it can gain 2.4 kB, which is 28% 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 6.8 kB or 78% of the original size.

Image Optimization

-15%

Potential reduce by 2.0 kB

  • Original 13.6 kB
  • After minification 11.6 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. Obviously, Unpossible needs image optimization as it can save up to 2.0 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-38%

Potential reduce by 10.7 kB

  • Original 28.0 kB
  • After minification 28.0 kB
  • After compression 17.2 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. Unpossible.co needs all CSS files to be minified and compressed as it can save up to 10.7 kB or 38% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

10

After Optimization

10

  • AJAX
  • Images
  • CSS

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

Network Requests Diagram

Accessibility Review

unpossible.co accessibility score

58

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

unpossible.co best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

unpossible.co SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unpossible.co 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 Unpossible.co main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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