Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

it.openlanguageexchange.com

Scambi Linguistici - Trova il tuo partner linguistico!

Page Load Speed

3.8 sec in total

First Response

330 ms

Resources Loaded

2.8 sec

Page Rendered

629 ms

it.openlanguageexchange.com screenshot

About Website

Welcome to it.openlanguageexchange.com homepage info - get ready to check It Openlanguageexchange best content for Austria right away, or after learning these important things about it.openlanguageexchange.com

Scambi Linguistici - Più di ✔123951 madrelingua che vogliono scambiare lingue. Scambio di conversazione - Online & Skype - nella vostra zona - Gratis!

Visit it.openlanguageexchange.com

Key Findings

We analyzed It.openlanguageexchange.com page load time and found that the first response time was 330 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

it.openlanguageexchange.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

it.openlanguageexchange.com

330 ms

it.openlanguageexchange.com

1150 ms

bootstrap.min.css

126 ms

bootstrap-select.min.css

241 ms

themify-icons.css

344 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 79% of them (23 requests) were addressed to the original It.openlanguageexchange.com, 7% (2 requests) were made to Ssl.google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain It.openlanguageexchange.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.8 kB (20%)

Content Size

207.8 kB

After Optimization

166.0 kB

In fact, the total size of It.openlanguageexchange.com main page is 207.8 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. 35% of websites need less resources to load. Javascripts take 94.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 39.4 kB

  • Original 47.7 kB
  • After minification 41.1 kB
  • After compression 8.3 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 6.6 kB, which is 14% 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 39.4 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 1.1 kB

  • Original 32.3 kB
  • After minification 31.2 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. It Openlanguageexchange images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 404 B

  • Original 94.6 kB
  • After minification 94.6 kB
  • After compression 94.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 933 B

  • Original 33.2 kB
  • After minification 33.2 kB
  • After compression 32.3 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. It.openlanguageexchange.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (59%)

Requests Now

17

After Optimization

7

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

Accessibility Review

it.openlanguageexchange.com accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

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

Links do not have a discernible name

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

it.openlanguageexchange.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

it.openlanguageexchange.com SEO score

78

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

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

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise It.openlanguageexchange.com can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that It.openlanguageexchange.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

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