Tools & Wizards About Us
oxtm-o2.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

oxtm-o2.com

Oxygen concentrator|portable oxygen concentrator|POC|O2|oxtm|Pules does oxygen concentrator|oxygen medical-Oxytek Medical Technology Co.,Ltd.

Page Load Speed

6.8 sec in total

First Response

1.3 sec

Resources Loaded

4.8 sec

Page Rendered

666 ms

oxtm-o2.com screenshot

About Website

Visit oxtm-o2.com now to see the best up-to-date Oxtm O2 content and also check out these interesting facts you probably never knew about oxtm-o2.com

Oxytek Medical Technology Co., Ltd. founded in 2015, which is the world-wide specialist in oxygen systems for medical, homecare, healthcare device company. We are not only created new generation of ox...

Visit oxtm-o2.com

Key Findings

We analyzed Oxtm-o2.com page load time and found that the first response time was 1.3 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

oxtm-o2.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value17.9 s

0/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

oxtm-o2.com

1303 ms

animate.min.css

655 ms

font-awesome.min.css

438 ms

swiper.min.css

437 ms

skin.css

1332 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that all of those requests were addressed to Oxtm-o2.com and no external sources were called. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Oxtm-o2.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 543.7 kB (9%)

Content Size

5.9 MB

After Optimization

5.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oxtm-o2.com main page is 5.9 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. 45% of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 38.5 kB

  • Original 44.3 kB
  • After minification 36.9 kB
  • After compression 5.8 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 7.4 kB, which is 17% 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 38.5 kB or 87% of the original size.

Image Optimization

-8%

Potential reduce by 450.0 kB

  • Original 5.6 MB
  • After minification 5.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. Oxtm O2 images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 27.0 kB

  • Original 118.7 kB
  • After minification 118.7 kB
  • After compression 91.7 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 27.0 kB or 23% of the original size.

CSS Optimization

-33%

Potential reduce by 28.1 kB

  • Original 85.1 kB
  • After minification 85.1 kB
  • After compression 56.9 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. Oxtm-o2.com needs all CSS files to be minified and compressed as it can save up to 28.1 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (8%)

Requests Now

37

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oxtm-o2.com

oxtm-o2.com

1303 ms

animate.min.css

animate.min.css

655 ms

font-awesome.min.css

font-awesome.min.css

438 ms

swiper.min.css

swiper.min.css

437 ms

skin.css

skin.css

1332 ms

logo.png

logo.png

661 ms

%E6%9C%AA%E6%A0%87%E9%A2%98-1(1).jpg

%E6%9C%AA%E6%A0%87%E9%A2%98-1(1).jpg

1992 ms

IMG_6127.jpg

IMG_6127.jpg

2406 ms

1445219605.jpg

1445219605.jpg

1093 ms

222.jpg

222.jpg

1547 ms

IMG_6141.jpg

IMG_6141.jpg

2697 ms

1445220263.jpg

1445220263.jpg

1316 ms

team_1.jpg

team_1.jpg

1336 ms

team_2.jpg

team_2.jpg

1539 ms

team_3.jpg

team_3.jpg

1559 ms

team_4.jpg

team_4.jpg

1761 ms

jquery.min.js

jquery.min.js

1782 ms

all_in_one_libs.min.js

all_in_one_libs.min.js

1792 ms

jquery.dlmenu.js

jquery.dlmenu.js

1981 ms

front.js

front.js

2005 ms

1123.jpg

1123.jpg

2090 ms

bb.jpg

bb.jpg

2420 ms

aaa.jpg

aaa.jpg

2233 ms

CE_2460_Certificate-1.jpg

CE_2460_Certificate-1.jpg

2477 ms

1444267436.jpg

1444267436.jpg

2262 ms

pricing_table_1.jpg

pricing_table_1.jpg

2468 ms

pricing_table_2.jpg

pricing_table_2.jpg

2486 ms

pricing_table_3.jpg

pricing_table_3.jpg

2625 ms

pricing_table_4.jpg

pricing_table_4.jpg

2640 ms

home_1_slider_1.jpg

home_1_slider_1.jpg

1581 ms

home_1_slider_2.jpg

home_1_slider_2.jpg

2035 ms

home_1_slider_3.jpg

home_1_slider_3.jpg

1634 ms

home_1_section_bg_1.jpg

home_1_section_bg_1.jpg

1738 ms

home_1_section_bg_2.jpg

home_1_section_bg_2.jpg

1969 ms

team_bg_1.jpg

team_bg_1.jpg

1790 ms

home_1_section_bg_3.jpg

home_1_section_bg_3.jpg

1849 ms

home_1_section_bg_4.jpg

home_1_section_bg_4.jpg

1863 ms

firasans-light-webfont.woff

firasans-light-webfont.woff

1898 ms

firasans-ultralight-webfont.woff

firasans-ultralight-webfont.woff

1962 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2096 ms

home_1_slider_4.jpg

home_1_slider_4.jpg

1225 ms

home_1_slider_5.jpg

home_1_slider_5.jpg

1369 ms

Accessibility Review

oxtm-o2.com accessibility score

59

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.

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

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

oxtm-o2.com best practices score

67

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

Page has valid source maps

SEO Factors

oxtm-o2.com SEO score

76

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

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oxtm-o2.com 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 Oxtm-o2.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

oxtm-o2.com

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