Tools & Wizards About Us
wdt-rf.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 29

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

wdt-rf.com

首页 赛迪讯科技,机器人cofdm高清双向无线图传设备,4K无线图传,高清无线微波,高清无线图像传输系统,高清无线移动视频传输,双向IP无线图传，无线图传设备租赁，无线微波设备租赁

Page Load Speed

13.4 sec in total

First Response

2.1 sec

Resources Loaded

10.8 sec

Page Rendered

458 ms

wdt-rf.com screenshot

About Website

Click here to check amazing Wdt Rf content. Otherwise, check out these important facts you probably never knew about wdt-rf.com

赛迪讯是研发与生产COFDM高清双向无线图传、4K超清无线图传、高清无线微波系统的公司，深入开发H.265应用于COFDM，用最小资源传输4K超清视频，产品已应用于电视直播，无人机，机器人，无人船等领域，并提供无线直播租赁服务，是当代无线通信产品首选.

Visit wdt-rf.com

Key Findings

We analyzed Wdt-rf.com page load time and found that the first response time was 2.1 sec and then it took 11.3 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

wdt-rf.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value24.7 s

0/100

10%

TBT (Total Blocking Time)

Value4,440 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.228

55/100

15%

TTI (Time to Interactive)

Value29.0 s

0/100

10%

Network Requests Diagram

wdt-rf.com

2117 ms

bootstrap.min.css

462 ms

font-awesome.min.css

450 ms

style.css

456 ms

-css.css

493 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 88% of them (90 requests) were addressed to the original Wdt-rf.com, 9% (9 requests) were made to Hm.baidu.com and 2% (2 requests) were made to Lermom.com.img.800cdn.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Wdt-rf.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.5 MB (41%)

Content Size

11.1 MB

After Optimization

6.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wdt-rf.com main page is 11.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 10.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 387.6 kB

  • Original 456.4 kB
  • After minification 444.4 kB
  • After compression 68.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. 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 387.6 kB or 85% of the original size.

Image Optimization

-40%

Potential reduce by 4.1 MB

  • Original 10.4 MB
  • After minification 6.3 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. Obviously, Wdt Rf needs image optimization as it can save up to 4.1 MB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 8.6 kB

  • Original 169.4 kB
  • After minification 169.4 kB
  • After compression 160.9 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

-40%

Potential reduce by 52.8 kB

  • Original 133.2 kB
  • After minification 125.8 kB
  • After compression 80.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. Wdt-rf.com needs all CSS files to be minified and compressed as it can save up to 52.8 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (33%)

Requests Now

78

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wdt Rf. 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 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wdt-rf.com

wdt-rf.com

2117 ms

bootstrap.min.css

bootstrap.min.css

462 ms

font-awesome.min.css

font-awesome.min.css

450 ms

style.css

style.css

456 ms

-css.css

-css.css

493 ms

-normalize.css

-normalize.css

494 ms

set2.css

set2.css

459 ms

-demoadpacks.css

-demoadpacks.css

725 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

929 ms

jquery-migrate-1.2.1.js

jquery-migrate-1.2.1.js

689 ms

wind.js

wind.js

741 ms

menu.js

menu.js

726 ms

jquery.js

jquery.js

976 ms

SuperEffects.js

SuperEffects.js

1181 ms

-public.js

-public.js

1002 ms

_hmproducts.css

_hmproducts.css

1015 ms

public.css

public.css

993 ms

slippry.css

slippry.css

1176 ms

public.js

public.js

2491 ms

bootstrap.min.js

bootstrap.min.js

1840 ms

frontend.js

frontend.js

1301 ms

slippry.min.js

slippry.min.js

1302 ms

index.html

index.html

229 ms

1054520142.jpg

1054520142.jpg

2513 ms

logo_sdison.png

logo_sdison.png

226 ms

mlogo.png

mlogo.png

229 ms

m1.png

m1.png

474 ms

m2.png

m2.png

455 ms

m3.png

m3.png

455 ms

m4.png

m4.png

462 ms

m5.png

m5.png

693 ms

1b197318d3438b7da69566598f96f84b.jpg

1b197318d3438b7da69566598f96f84b.jpg

1712 ms

cf1644d07ab49be2361c017d1e60f55c.jpg

cf1644d07ab49be2361c017d1e60f55c.jpg

1190 ms

052880c6a86193d1ab68e2b4406d8b3e.jpg

052880c6a86193d1ab68e2b4406d8b3e.jpg

1486 ms

ee0981d929b5954be1533226dfb288ab.jpg

ee0981d929b5954be1533226dfb288ab.jpg

2041 ms

960fb134ec03f3759c10abf4e5eb2b5d.jpg

960fb134ec03f3759c10abf4e5eb2b5d.jpg

1890 ms

btnL.png

btnL.png

1952 ms

btnL2.png

btnL2.png

1500 ms

btnR.png

btnR.png

1698 ms

btnR2.png

btnR2.png

1740 ms

proBor.png

proBor.png

1936 ms

proBor2.png

proBor2.png

1950 ms

b0565dbffebf63975a5d690ecfb16742.jpg

b0565dbffebf63975a5d690ecfb16742.jpg

1995 ms

0ce46f043f037b037feca060ca4e2a8f.png

0ce46f043f037b037feca060ca4e2a8f.png

4818 ms

985ad25b46dc767b6ba8064f864aba03.png

985ad25b46dc767b6ba8064f864aba03.png

4298 ms

5eb4a87abb8f339295d405d7fc99d02a.png

5eb4a87abb8f339295d405d7fc99d02a.png

3589 ms

3445f2da2fc0ec9e1e438b2a97174416.jpg

3445f2da2fc0ec9e1e438b2a97174416.jpg

2236 ms

ae359e554df9491f6f2019bf9e4fd75f.jpg

ae359e554df9491f6f2019bf9e4fd75f.jpg

2476 ms

e7406c01c654acb129e18f8e4afb0241.jpg

e7406c01c654acb129e18f8e4afb0241.jpg

2514 ms

1915a1cc6471952dad247aee175ab50e.png

1915a1cc6471952dad247aee175ab50e.png

2707 ms

142eedbd91b78e7632e2b7b935b5728e.png

142eedbd91b78e7632e2b7b935b5728e.png

3682 ms

60f512f102d5f962225d0fd086a125b4.jpg

60f512f102d5f962225d0fd086a125b4.jpg

3237 ms

d3ca476fa0b7e078fa4813e54c0e5b46.jpg

d3ca476fa0b7e078fa4813e54c0e5b46.jpg

2946 ms

a200da1d03b8c19f7fd3e9e6e37a6ba3.png

a200da1d03b8c19f7fd3e9e6e37a6ba3.png

4877 ms

bootstrap.min.css

bootstrap.min.css

3993 ms

font-awesome.min.css

font-awesome.min.css

3762 ms

style.css

style.css

3768 ms

public.css

public.css

1083 ms

style.css

style.css

1083 ms

-css.css

-css.css

4365 ms

-normalize.css

-normalize.css

3742 ms

set2.css

set2.css

3795 ms

-demoadpacks.css

-demoadpacks.css

4022 ms

_hmproducts.css

_hmproducts.css

4105 ms

public.css

public.css

3925 ms

slippry.css

slippry.css

4029 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3609 ms

foot_teltime.png

foot_teltime.png

194 ms

hm.js

hm.js

958 ms

v.js

v.js

0 ms

hm.js

hm.js

0 ms

jquery.js

jquery.js

1 ms

d1157ee3906dea61268844e32341c179.png

d1157ee3906dea61268844e32341c179.png

5240 ms

hm.js

hm.js

1 ms

58f1647cf456336de260496349e4a0e7.png

58f1647cf456336de260496349e4a0e7.png

5885 ms

islogin.html

islogin.html

3634 ms

public.css

public.css

3536 ms

style.css

style.css

3527 ms

hm.js

hm.js

3515 ms

jquery.js

jquery.js

3502 ms

jquery.particleground.min.js

jquery.particleground.min.js

3367 ms

86e2fbe5b078b2fa9b405e0a737b81dc.png

86e2fbe5b078b2fa9b405e0a737b81dc.png

3670 ms

0aad35ccc976b09b787f800b27bcb75e.jpg

0aad35ccc976b09b787f800b27bcb75e.jpg

3792 ms

022bee33a9a72311d3c4e4332100422a.jpg

022bee33a9a72311d3c4e4332100422a.jpg

4800 ms

f1ebf0c3cd9f4acd721788ac948e3e78.jpg

f1ebf0c3cd9f4acd721788ac948e3e78.jpg

4025 ms

f15e994514306e2f06e8ef7fe4a4b7fe.jpg

f15e994514306e2f06e8ef7fe4a4b7fe.jpg

4071 ms

d162d9dc5ab29604364941ffffc71e0b.jpg

d162d9dc5ab29604364941ffffc71e0b.jpg

3958 ms

hm.gif

hm.gif

311 ms

f231b91b5e4587eec0e6805be0787787.jpg

f231b91b5e4587eec0e6805be0787787.jpg

4958 ms

dm.png

dm.png

4072 ms

615125d4337ac710ad94ad456ed9b42d.jpg

615125d4337ac710ad94ad456ed9b42d.jpg

3755 ms

ad2f8fbaabb63dbdac990cdfe0d2c15c.jpg

ad2f8fbaabb63dbdac990cdfe0d2c15c.jpg

3980 ms

foot_erwm.png

foot_erwm.png

3561 ms

sy-loader.gif

sy-loader.gif

3210 ms

foot_teltime.png

foot_teltime.png

96 ms

hm.gif

hm.gif

451 ms

hm.js

hm.js

315 ms

hm.gif

hm.gif

445 ms

hm.gif

hm.gif

446 ms

hm.gif

hm.gif

332 ms

hm.gif

hm.gif

635 ms

hm.gif

hm.gif

848 ms

Accessibility Review

wdt-rf.com accessibility score

29

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

wdt-rf.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wdt-rf.com 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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wdt-rf.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Wdt-rf.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

wdt-rf.com

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