Tools & Wizards About Us
dullr.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

dullr.com

篆体时刻_篆体字转换器_小篆字体字典_大篆刻印章生成-杜拉拉篆体时刻

Page Load Speed

39 sec in total

First Response

2.2 sec

Resources Loaded

36.5 sec

Page Rendered

327 ms

dullr.com screenshot

About Website

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

杜拉拉篆书艺术网主要提供篆体字转换器可以轻松的将中文转换成篆书字体,大符篆师,小篆字体,篆书字典,篆书字体,篆刻字体,篆体字查询,篆刻印章,小篆字帖,篆刻入门,吴昌硕篆刻,小篆字体下载,篆刻作品等等提供多种篆书在线转换字体！

Visit dullr.com

Key Findings

We analyzed Dullr.com page load time and found that the first response time was 2.2 sec and then it took 36.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

dullr.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value18.2 s

0/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.161

73/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

dullr.com

2202 ms

www.dullr.com

2543 ms

bootstrap.min.css

3474 ms

style.css

860 ms

f.js

2138 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 33% of them (27 requests) were addressed to the original Dullr.com, 16% (13 requests) were made to Pos.baidu.com and 14% (12 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Cm.jd.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 471.7 kB (35%)

Content Size

1.4 MB

After Optimization

884.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dullr.com main page is 1.4 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. 40% of websites need less resources to load. Images take 661.2 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 41.1 kB

  • Original 47.2 kB
  • After minification 44.4 kB
  • After compression 6.1 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 41.1 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 11.0 kB

  • Original 661.2 kB
  • After minification 650.2 kB

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. Dullr images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 297.6 kB

  • Original 503.6 kB
  • After minification 503.6 kB
  • After compression 206.0 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 297.6 kB or 59% of the original size.

CSS Optimization

-85%

Potential reduce by 122.0 kB

  • Original 144.0 kB
  • After minification 142.5 kB
  • After compression 22.0 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. Dullr.com needs all CSS files to be minified and compressed as it can save up to 122.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (40%)

Requests Now

77

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dullr.com

dullr.com

2202 ms

www.dullr.com

www.dullr.com

2543 ms

bootstrap.min.css

bootstrap.min.css

3474 ms

style.css

style.css

860 ms

f.js

f.js

2138 ms

i.js

i.js

2138 ms

c.js

c.js

2159 ms

stat.php

stat.php

2257 ms

jquery.min.js

jquery.min.js

608 ms

bootstrap.min.js

bootstrap.min.js

579 ms

javascript.js

javascript.js

1273 ms

qcmm

qcmm

829 ms

ui

ui

1705 ms

minifanzhuanshu.png

minifanzhuanshu.png

482 ms

jingdianfanjiaozhuan.png

jingdianfanjiaozhuan.png

458 ms

jingdianfanfangzhuan.png

jingdianfanfangzhuan.png

452 ms

jinwendazhuan.png

jinwendazhuan.png

892 ms

hanyizhuanshufan.png

hanyizhuanshufan.png

892 ms

hanyicuzhuanfan.png

hanyicuzhuanfan.png

930 ms

fangzhengxiaozhuanti.png

fangzhengxiaozhuanti.png

6858 ms

minijianwawazhuan.png

minijianwawazhuan.png

1155 ms

yegenyouxinzhuan.png

yegenyouxinzhuan.png

3659 ms

jingdianfanyinzhuan.png

jingdianfanyinzhuan.png

1388 ms

baizhouzhuangu.png

baizhouzhuangu.png

2731 ms

huakangxinzhuan.png

huakangxinzhuan.png

2797 ms

tangrenjianzhuan.png

tangrenjianzhuan.png

1733 ms

fangzhengxuanzhenzhuanbian.png

fangzhengxuanzhenzhuanbian.png

1820 ms

wanghanzongyinzhuanti.png

wanghanzongyinzhuanti.png

2292 ms

chaoshijicufangzhuan.png

chaoshijicufangzhuan.png

2275 ms

chaoshijicujiaozhuan.png

chaoshijicujiaozhuan.png

2683 ms

chaoshijicuyinzhuan.png

chaoshijicuyinzhuan.png

7323 ms

chaoshijixifangzhuan.png

chaoshijixifangzhuan.png

4787 ms

chaoshijixijiaozhuan.png

chaoshijixijiaozhuan.png

4828 ms

chaoshijixiyinzhuan.png

chaoshijixiyinzhuan.png

3716 ms

qcmm

qcmm

890 ms

qcmm

qcmm

1290 ms

qcmm

qcmm

1071 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

8928 ms

qcmm

qcmm

1023 ms

qcmm

qcmm

1095 ms

stat.htm

stat.htm

756 ms

core.php

core.php

1869 ms

qcmm

qcmm

1430 ms

qcmm

qcmm

683 ms

qcmm

qcmm

639 ms

qcmm

qcmm

534 ms

qcmm

qcmm

1626 ms

cm.gif

cm.gif

1797 ms

adx.php

adx.php

1270 ms

reduce_bd-logo1_oper.png

reduce_bd-logo1_oper.png

543 ms

cpro.js

cpro.js

2236 ms

sync.htm

sync.htm

524 ms

time.js

time.js

532 ms

adx.php

adx.php

1295 ms

adPic.new.20150909.min.js

adPic.new.20150909.min.js

126 ms

bot-patch.min.js

bot-patch.min.js

138 ms

click.min.js

click.min.js

139 ms

adx.php

adx.php

2187 ms

rBEhWlJYrAEIAAAAAAACetYAYQwAAECuwP__W4AAAKS951.png

rBEhWlJYrAEIAAAAAAACetYAYQwAAECuwP__W4AAAKS951.png

576 ms

5707eb01N6d56c747.jpg

5707eb01N6d56c747.jpg

602 ms

adx.php

adx.php

1642 ms

adx.php

adx.php

1726 ms

9.gif

9.gif

1120 ms

sync_pos.htm

sync_pos.htm

394 ms

sync2r.htm

sync2r.htm

1689 ms

app.gif

app.gif

902 ms

youku

youku

1071 ms

closefeedback.min.js

closefeedback.min.js

520 ms

bd-logo1.png

bd-logo1.png

526 ms

du

du

20217 ms

reduce_promotion_oper.png

reduce_promotion_oper.png

480 ms

bd_logo.png

bd_logo.png

532 ms

bg_rb.png

bg_rb.png

550 ms

closefeedback.min.js

closefeedback.min.js

483 ms

closeBtn_oper.png

closeBtn_oper.png

803 ms

promotionLeftBottom.png

promotionLeftBottom.png

5120 ms

nopic.jpg

nopic.jpg

557 ms

55e40d3fN2a01189f.png

55e40d3fN2a01189f.png

184 ms

o.htm

o.htm

1039 ms

ac.js

ac.js

548 ms

wh.js

wh.js

871 ms

fp.htm

fp.htm

1940 ms

fp.htm

fp.htm

1207 ms

Accessibility Review

dullr.com accessibility score

76

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 IDs are not unique

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

Form elements do not have associated labels

Best Practices

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

dullr.com SEO score

80

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dullr.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Dullr.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

dullr.com

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