Tools & Wizards About Us
teampel.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

teampel.com

On-premises Collaboration Software for Business │ Teampel

Page Load Speed

8.8 sec in total

First Response

506 ms

Resources Loaded

7.8 sec

Page Rendered

560 ms

teampel.com screenshot

About Website

Welcome to teampel.com homepage info - get ready to check Teampel best content for Taiwan right away, or after learning these important things about teampel.com

An intranet-capable solution, Teampel is all your teamwork essentials in one place: projects, messaging and data analysis. Start using private cloud for your business today.

Visit teampel.com

Key Findings

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

Performance Metrics

teampel.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.6 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value730 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

teampel.com

506 ms

teampel.com

980 ms

en

499 ms

index.css

245 ms

objectFitPolyfill.min.js

489 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 75% of them (76 requests) were addressed to the original Teampel.com, 12% (12 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Teampel.com.

Page Optimization Overview & Recommendations

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

Content Size

2.7 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Teampel.com main page is 2.7 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. Only a small number of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 43.3 kB

  • Original 52.0 kB
  • After minification 33.1 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 18.9 kB, which is 36% 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 43.3 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 201.7 kB

  • Original 2.4 MB
  • After minification 2.2 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. Teampel images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 88.6 kB

  • Original 193.0 kB
  • After minification 193.0 kB
  • After compression 104.4 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 88.6 kB or 46% of the original size.

CSS Optimization

-18%

Potential reduce by 10.8 kB

  • Original 58.9 kB
  • After minification 58.9 kB
  • After compression 48.1 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. Teampel.com needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (37%)

Requests Now

81

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

teampel.com

teampel.com

506 ms

teampel.com

teampel.com

980 ms

en

en

499 ms

index.css

index.css

245 ms

objectFitPolyfill.min.js

objectFitPolyfill.min.js

489 ms

bootstrap.css

bootstrap.css

984 ms

jstyle.css

jstyle.css

1209 ms

animationLayout.css

animationLayout.css

966 ms

resource.css

resource.css

968 ms

media.css

media.css

969 ms

slider-pro.css

slider-pro.css

1000 ms

features.css

features.css

1207 ms

select.css

select.css

1212 ms

toggle.css

toggle.css

1213 ms

cht_lang.css

cht_lang.css

1223 ms

jquery-1.12.0.js

jquery-1.12.0.js

2256 ms

jquery.sliderPro.js

jquery.sliderPro.js

1950 ms

jquery.validate.js

jquery.validate.js

1453 ms

bootstrap.min.js

bootstrap.min.js

1450 ms

react.development.js

react.development.js

37 ms

react-dom.development.js

react-dom.development.js

49 ms

jstyle.js

jstyle.js

1451 ms

jcarousel.js

jcarousel.js

1459 ms

selectize.js

selectize.js

1940 ms

download.js

download.js

1689 ms

react.development.js

react.development.js

23 ms

react-dom.development.js

react-dom.development.js

26 ms

cwtexhei.css

cwtexhei.css

32 ms

css

css

24 ms

gtm.js

gtm.js

282 ms

fbevents.js

fbevents.js

121 ms

sa.js

sa.js

858 ms

api.ipdata.co

api.ipdata.co

350 ms

close.png

close.png

430 ms

logo.png

logo.png

364 ms

ui-01.png

ui-01.png

1032 ms

ui-02.png

ui-02.png

1270 ms

ui-03.png

ui-03.png

812 ms

ui-04.png

ui-04.png

815 ms

qa1.png

qa1.png

362 ms

qa2-1200.png

qa2-1200.png

806 ms

qa3.png

qa3.png

807 ms

qa4-1200.png

qa4-1200.png

816 ms

qa2-768.png

qa2-768.png

817 ms

qa4-768.png

qa4-768.png

823 ms

qa2-576.png

qa2-576.png

1032 ms

qa4-576.png

qa4-576.png

1041 ms

illustration.png

illustration.png

1757 ms

01-1.png

01-1.png

1059 ms

01-2.png

01-2.png

1271 ms

01-3.png

01-3.png

1270 ms

02-1.png

02-1.png

1283 ms

02-2.png

02-2.png

1307 ms

02-3.png

02-3.png

1508 ms

03-1.png

03-1.png

1509 ms

03-2.png

03-2.png

1509 ms

03-3.png

03-3.png

1524 ms

04-1.png

04-1.png

1555 ms

04-2.png

04-2.png

1749 ms

04-3.png

04-3.png

1747 ms

05-1.png

05-1.png

1749 ms

05-2.png

05-2.png

1764 ms

05-3.png

05-3.png

1804 ms

06-1.png

06-1.png

1986 ms

06-2.png

06-2.png

1986 ms

06-3.png

06-3.png

1987 ms

tw.png

tw.png

2712 ms

bubble.svg

bubble.svg

2001 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz76CyzC1Esg.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz76CyzC1Esg.ttf

308 ms

NotoSansTC-Regular.woff

NotoSansTC-Regular.woff

467 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz75KyzC1Esg.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz75KyzC1Esg.ttf

375 ms

NotoSansTC-Medium.woff

NotoSansTC-Medium.woff

477 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz7_6yzC1Esg.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz7_6yzC1Esg.ttf

372 ms

NotoSansTC-Light.woff

NotoSansTC-Light.woff

476 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz76CzzC1Esg.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz76CzzC1Esg.ttf

377 ms

NotoSansTC-Thin.woff

NotoSansTC-Thin.woff

470 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz70e1zC1Esg.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz70e1zC1Esg.ttf

379 ms

NotoSansTC-Bold.woff

NotoSansTC-Bold.woff

477 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz7wm1zC1Esg.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz7wm1zC1Esg.ttf

460 ms

NotoSansTC-Black.woff

NotoSansTC-Black.woff

480 ms

down-arrow-w.png

down-arrow-w.png

1984 ms

ico_play.svg

ico_play.svg

2156 ms

bg-banner.png

bg-banner.png

2824 ms

left-arrow.png

left-arrow.png

1871 ms

close.png

close.png

672 ms

right-arrow.png

right-arrow.png

1444 ms

bg-pattern.png

bg-pattern.png

1496 ms

bg-noise.png

bg-noise.png

1659 ms

rectangle-1.png

rectangle-1.png

1657 ms

rectangle-2.png

rectangle-2.png

1676 ms

rectangle-3.png

rectangle-3.png

1736 ms

rectangle-4.png

rectangle-4.png

1889 ms

rectangle-5.png

rectangle-5.png

1682 ms

rectangle-6.png

rectangle-6.png

1700 ms

rectangle-7.png

rectangle-7.png

1765 ms

rectangle-8.png

rectangle-8.png

1892 ms

close.png

close.png

1111 ms

rectangle-9.png

rectangle-9.png

1684 ms

bg-media.png

bg-media.png

2169 ms

fists.png

fists.png

1703 ms

top.png

top.png

1771 ms

Accessibility Review

teampel.com accessibility score

72

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

button, link, and menuitem elements do not have accessible names.

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

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

High

Links do not have a discernible name

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

teampel.com best practices score

58

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

teampel.com SEO score

87

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

Image elements do not have [alt] attributes

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

teampel.com

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