Tools & Wizards About Us
tandem.net screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

tandem.net

Tandem Language Exchange App | Find Conversation Exchange Partners

Page Load Speed

4.5 sec in total

First Response

196 ms

Resources Loaded

3.1 sec

Page Rendered

1.2 sec

tandem.net screenshot

About Website

Welcome to tandem.net homepage info - get ready to check Tandem best content for China right away, or after learning these important things about tandem.net

Find A Language Exchange Partner Online! ✓ Connect With Other Language Learners ✓ Learn From Native Speakers For Free ✓ Join The Best Conversation Exchange Community ✓ Become Fluent With Tandem!

Visit tandem.net

Key Findings

We analyzed Tandem.net page load time and found that the first response time was 196 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

tandem.net performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.272

45/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

tandem.net

196 ms

tandem.net

566 ms

04d02d1e6ba895e9.css

372 ms

c1d96caff5dd649c.css

409 ms

polyfills-78c92fac7aa8fdd8.js

394 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 98% of them (86 requests) were addressed to the original Tandem.net, 2% (2 requests) were made to Images.ctfassets.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Tandem.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.6 kB (13%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images

In fact, the total size of Tandem.net main page is 1.8 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 214.9 kB

  • Original 271.5 kB
  • After minification 271.4 kB
  • After compression 56.6 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 214.9 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 12.7 kB

  • Original 1.5 MB
  • After minification 1.5 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. Tandem images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 20 (23%)

Requests Now

86

After Optimization

66

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tandem.net

tandem.net

196 ms

tandem.net

tandem.net

566 ms

04d02d1e6ba895e9.css

04d02d1e6ba895e9.css

372 ms

c1d96caff5dd649c.css

c1d96caff5dd649c.css

409 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

394 ms

webpack-a564e35eac45e556.js

webpack-a564e35eac45e556.js

284 ms

framework-9620da855a94eb57.js

framework-9620da855a94eb57.js

496 ms

main-43ed1583751f0b2e.js

main-43ed1583751f0b2e.js

416 ms

_app-66ec95e9bc05df0f.js

_app-66ec95e9bc05df0f.js

877 ms

592-a5e3ba24041ed01d.js

592-a5e3ba24041ed01d.js

501 ms

577-6c228109f7237640.js

577-6c228109f7237640.js

502 ms

53-7964a701c3fe5ebf.js

53-7964a701c3fe5ebf.js

503 ms

index-ee7c2fe2fbd466df.js

index-ee7c2fe2fbd466df.js

502 ms

_buildManifest.js

_buildManifest.js

569 ms

_ssgManifest.js

_ssgManifest.js

569 ms

image

image

571 ms

image

image

569 ms

image

image

572 ms

image

image

665 ms

image

image

664 ms

image

image

666 ms

image

image

672 ms

homepage_hero_bg2.png

homepage_hero_bg2.png

127 ms

homepage_desktop.png

homepage_desktop.png

16 ms

image

image

662 ms

image

image

755 ms

image

image

756 ms

image

image

846 ms

image

image

758 ms

image

image

849 ms

image

image

1015 ms

image

image

929 ms

image

image

928 ms

image

image

942 ms

image

image

946 ms

image

image

962 ms

image

image

1023 ms

image

image

1026 ms

image

image

1046 ms

image

image

968 ms

image

image

786 ms

image

image

735 ms

image

image

899 ms

image

image

805 ms

image

image

649 ms

image

image

650 ms

image

image

662 ms

image

image

718 ms

image

image

749 ms

image

image

750 ms

image

image

696 ms

image

image

747 ms

image

image

743 ms

image

image

771 ms

image

image

772 ms

image

image

700 ms

image

image

740 ms

image

image

742 ms

image

image

741 ms

image

image

755 ms

image

image

678 ms

image

image

1611 ms

image

image

737 ms

image

image

651 ms

image

image

648 ms

image

image

765 ms

image

image

599 ms

image

image

660 ms

image

image

649 ms

image

image

643 ms

image

image

856 ms

image

image

803 ms

image

image

802 ms

image

image

801 ms

image

image

778 ms

image

image

1037 ms

image

image

1045 ms

image

image

991 ms

image

image

956 ms

image

image

966 ms

image

image

1027 ms

image

image

978 ms

image

image

1006 ms

image

image

977 ms

image

image

975 ms

image

image

1023 ms

image

image

981 ms

image

image

1003 ms

Accessibility Review

tandem.net accessibility score

97

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.

Best Practices

tandem.net best practices score

83

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

tandem.net SEO score

97

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

    EN

  • Encoding

    UTF-8

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

tandem.net

Open Graph data is detected on the main page of Tandem. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: