Tools & Wizards About Us

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

tamron.com.cn

TAMRON 腾龙镜头 中国官方网站

Page Load Speed

15.5 sec in total

First Response

686 ms

Resources Loaded

14.3 sec

Page Rendered

450 ms

About Website

Welcome to tamron.com.cn homepage info - get ready to check TAMRON best content for China right away, or after learning these important things about tamron.com.cn

腾龙正式成立腾龙光学（上海）有限公司，自2006在中国成立以来以满足顾客、为顾客提供高品质、高信赖度、高性能的镜头为主旨，孜孜不倦、精益求精地实行技术研究和开发，成就为一家以技术为资本的综合性专业光学制造商。

Visit tamron.com.cn

Key Findings

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

Performance Metrics

tamron.com.cn performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value1.362

0/100

15%

TTI (Time to Interactive)

Value5.4 s

71/100

10%

Network Requests Diagram

tamron.com.cn

686 ms

tamron.com.cn

900 ms

css

28 ms

style.css

440 ms

moment.min.js

659 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 96% of them (82 requests) were addressed to the original Tamron.com.cn, 2% (2 requests) were made to Hm.baidu.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (10.8 sec) belongs to the original domain Tamron.com.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.7 kB (7%)

Content Size

5.1 MB

After Optimization

4.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tamron.com.cn main page is 5.1 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. 65% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 38.6 kB

  • Original 46.4 kB
  • After minification 39.4 kB
  • After compression 7.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.1 kB, which is 15% 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.6 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 219.9 kB

  • Original 4.8 MB
  • After minification 4.6 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. TAMRON images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 101.1 kB

  • Original 189.7 kB
  • After minification 189.6 kB
  • After compression 88.6 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 101.1 kB or 53% of the original size.

CSS Optimization

-47%

Potential reduce by 14.0 kB

  • Original 29.6 kB
  • After minification 29.6 kB
  • After compression 15.6 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. Tamron.com.cn needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (15%)

Requests Now

82

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

tamron.com.cn 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

[aria-*] attributes do not match their roles

High

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

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

tamron.com.cn best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

tamron.com.cn SEO score

88

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

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tamron.com.cn can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Tamron.com.cn 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 TAMRON. 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: