Tools & Wizards About Us
dralar.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

dralar.com

易游网页版-易游(中国)

Page Load Speed

14 sec in total

First Response

930 ms

Resources Loaded

12.4 sec

Page Rendered

672 ms

dralar.com screenshot

About Website

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

易游网页版（以下简称易游(中国)）成立于2003年8月，是由自治区国资委履行出资人职责的国有独资企业，截至2020年12月，资产总额1285亿元，以生态环保、绿色食品、资本运营和资产管理为主业。易游网页版将继续坚持“与时俱进、认真求实、团结协作、快乐工作”的核心价值观，坚持“提供优质环保钢管，改善人类生活环境，引领促进行业发展”的使命，用心塑造郑州京华特色的“华岐”品牌。

Visit dralar.com

Key Findings

We analyzed Dralar.com page load time and found that the first response time was 930 ms and then it took 13.1 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

dralar.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value590 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

dralar.com

930 ms

dralar.com

885 ms

www.dralar.com

424 ms

www.dralar.com

1094 ms

ky.js

1363 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 49% of them (48 requests) were addressed to the original Dralar.com, 29% (28 requests) were made to Slb5288.com and 5% (5 requests) were made to Plugin.tianqistatic.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Slb5288.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 268.5 kB (2%)

Content Size

11.5 MB

After Optimization

11.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 31.8 kB

  • Original 42.6 kB
  • After minification 41.3 kB
  • After compression 10.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 31.8 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 222.5 kB

  • Original 11.2 MB
  • After minification 11.0 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. Dralar images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 9.4 kB

  • Original 147.5 kB
  • After minification 147.5 kB
  • After compression 138.1 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

-8%

Potential reduce by 4.9 kB

  • Original 63.7 kB
  • After minification 63.7 kB
  • After compression 58.8 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. Dralar.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (19%)

Requests Now

86

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dralar.com

dralar.com

930 ms

dralar.com

dralar.com

885 ms

www.dralar.com

www.dralar.com

424 ms

www.dralar.com

www.dralar.com

1094 ms

ky.js

ky.js

1363 ms

default.css

default.css

216 ms

jquery.min.js

jquery.min.js

437 ms

qrcode.js

qrcode.js

658 ms

jquery.SuperSlide.2.1.1.js

jquery.SuperSlide.2.1.1.js

665 ms

Flash-banner.js

Flash-banner.js

659 ms

1.js

1.js

667 ms

focuspic.js

focuspic.js

678 ms

swfobject.js

swfobject.js

701 ms

comm.js

comm.js

881 ms

ky.js

ky.js

1118 ms

hm.js

hm.js

1218 ms

ky.html

ky.html

211 ms

newlogo.jpg

newlogo.jpg

215 ms

W020240201585285010198.jpg

W020240201585285010198.jpg

2327 ms

W020240201621544879571.jpg

W020240201621544879571.jpg

1965 ms

W020240201622361551213.png

W020240201622361551213.png

229 ms

W020240201622568303199.jpg

W020240201622568303199.jpg

875 ms

W020170620583865111111.jpg

W020170620583865111111.jpg

889 ms

W020210730627520786645.jpg

W020210730627520786645.jpg

860 ms

W020230419587262565466.png

W020230419587262565466.png

456 ms

W020230222800021874118.png

W020230222800021874118.png

1755 ms

W020230222799898321375.png

W020230222799898321375.png

1919 ms

W020221016710202357038.jpg

W020221016710202357038.jpg

1315 ms

W020220411410056782886.jpg

W020220411410056782886.jpg

1115 ms

W020220302415533903930.jpg

W020220302415533903930.jpg

1788 ms

W020240417653687337106.jpg

W020240417653687337106.jpg

1538 ms

W020240316345868537283.jpg

W020240316345868537283.jpg

1761 ms

W020231123601021526589.jpg

W020231123601021526589.jpg

1975 ms

W020230414541343674682.jpg

W020230414541343674682.jpg

1985 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

940 ms

W020240809658371577543.jpg

W020240809658371577543.jpg

2003 ms

W020240809658067794274.jpg

W020240809658067794274.jpg

2171 ms

W020240509637963727966.jpg

W020240509637963727966.jpg

2171 ms

W020240201650693010620.jpg

W020240201650693010620.jpg

2182 ms

W020230427656632391052.jpg

W020230427656632391052.jpg

2411 ms

1pxshadow.png

1pxshadow.png

2202 ms

fangdj.gif

fangdj.gif

2312 ms

navLine.gif

navLine.gif

2364 ms

index.php

index.php

779 ms

body-bg.jpg

body-bg.jpg

2366 ms

ico.png

ico.png

2417 ms

tupiain_bg.jpg

tupiain_bg.jpg

2507 ms

loading.gif

loading.gif

2531 ms

icon_1.gif

icon_1.gif

2578 ms

i_icos.png

i_icos.png

2560 ms

1px.png

1px.png

2575 ms

libg.gif

libg.gif

2616 ms

f_sear_btn.png

f_sear_btn.png

2714 ms

z_stat.php

z_stat.php

1180 ms

hm.gif

hm.gif

309 ms

jquery.min.js

jquery.min.js

424 ms

cslink.js

cslink.js

632 ms

main.css

main.css

1914 ms

cslink.js

cslink.js

236 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

367 ms

new_zishiying.css

new_zishiying.css

332 ms

jquery.provincesCity.js

jquery.provincesCity.js

334 ms

provincesData.js

provincesData.js

383 ms

b0.png

b0.png

133 ms

hm.js

hm.js

328 ms

stat.htm

stat.htm

1334 ms

c.js

c.js

835 ms

hm.gif

hm.gif

306 ms

pic.gif

pic.gif

1107 ms

sidefloat.png

sidefloat.png

688 ms

shell_v2.js

shell_v2.js

716 ms

background.png

background.png

1708 ms

ag-66-4.png

ag-66-4.png

2393 ms

ldlogo.png

ldlogo.png

1841 ms

milanlogo.png

milanlogo.png

1713 ms

xingkonglogo.png

xingkonglogo.png

717 ms

htylogo.png

htylogo.png

2374 ms

anbologo.png

anbologo.png

926 ms

jiuyoulogo.png

jiuyoulogo.png

1566 ms

mklogo.png

mklogo.png

1776 ms

sport-item-bg.png

sport-item-bg.png

1919 ms

1.png

1.png

4413 ms

rbsmgwmigzeaqeisaabdvano3pe24.webp

rbsmgwmigzeaqeisaabdvano3pe24.webp

2726 ms

rbsmgwmig0oaqpqmaabq2kzlptk31.webp

rbsmgwmig0oaqpqmaabq2kzlptk31.webp

2815 ms

rbsmgwmigyqad1n-aaa_2muwpem57.webp

rbsmgwmigyqad1n-aaa_2muwpem57.webp

2129 ms

rbsmgwmmnw-ahnf9aabt7ce2zgq87.webp

rbsmgwmmnw-ahnf9aabt7ce2zgq87.webp

3163 ms

sj.png

sj.png

3030 ms

latin.fab57614.woff2

latin.fab57614.woff2

2604 ms

montserrat-regular.949efd65.ttf

montserrat-regular.949efd65.ttf

2817 ms

iconfont.e7187704.woff

iconfont.e7187704.woff

2933 ms

montserrat-black.be2a4b98.ttf

montserrat-black.be2a4b98.ttf

3032 ms

logger.js

logger.js

233 ms

bds_s_v2.js

bds_s_v2.js

493 ms

bdsstyle.css

bdsstyle.css

215 ms

is.png

is.png

257 ms

iconfont.e7187704.woff2

iconfont.e7187704.woff2

420 ms

iconfont.e7187704.ttf

iconfont.e7187704.ttf

210 ms

Accessibility Review

dralar.com accessibility score

51

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

[id] attributes on active, focusable elements are not unique

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

<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

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

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

dralar.com best practices score

50

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

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dralar.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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 Dralar.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 Dralar.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

dralar.com

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