Tools & Wizards About Us
dev.camscanner.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

dev.camscanner.com

CamScanner Developers | Power your app with intelligent document scanning.

Page Load Speed

2.5 sec in total

First Response

642 ms

Resources Loaded

1.7 sec

Page Rendered

163 ms

dev.camscanner.com screenshot

About Website

Click here to check amazing Dev Cam Scanner content for China. Otherwise, check out these important facts you probably never knew about dev.camscanner.com

CamScanner Developers，Open API，power your app with intelligent document scanning and enable your apps to digitalize paper documents with cutting-edge image processing technologies.

Visit dev.camscanner.com

Key Findings

We analyzed Dev.camscanner.com page load time and found that the first response time was 642 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

dev.camscanner.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

dev.camscanner.com

642 ms

dev.camscanner.com

858 ms

cs-09ab1a.css

73 ms

cs-dev-guide-cc4244.css

89 ms

cs-header-12f5b8.js

80 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Dev.camscanner.com, 93% (27 requests) were made to Static.intsig.net. The less responsive or slowest element that took the longest time to load (858 ms) belongs to the original domain Dev.camscanner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.8 kB (3%)

Content Size

292.8 kB

After Optimization

282.9 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Dev.camscanner.com main page is 292.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 272.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 7.7 kB

  • Original 10.2 kB
  • After minification 7.9 kB
  • After compression 2.6 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 2.3 kB, which is 22% 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 7.7 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 3 B

  • Original 272.5 kB
  • After minification 272.5 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. Dev Cam Scanner images are well optimized though.

CSS Optimization

-22%

Potential reduce by 2.2 kB

  • Original 10.1 kB
  • After minification 10.1 kB
  • After compression 7.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. Dev.camscanner.com needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 22% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dev.camscanner.com

dev.camscanner.com

642 ms

dev.camscanner.com

dev.camscanner.com

858 ms

cs-09ab1a.css

cs-09ab1a.css

73 ms

cs-dev-guide-cc4244.css

cs-dev-guide-cc4244.css

89 ms

cs-header-12f5b8.js

cs-header-12f5b8.js

80 ms

cs-footer-50a274.js

cs-footer-50a274.js

87 ms

cs-dev-guide-478213.js

cs-dev-guide-478213.js

78 ms

openapi_logo.png

openapi_logo.png

25 ms

openapi_head_twitter.png

openapi_head_twitter.png

19 ms

openapi_head_fb.png

openapi_head_fb.png

15 ms

openapi_head_google.png

openapi_head_google.png

14 ms

openapi_banner.png

openapi_banner.png

17 ms

openapi_btn_applynow.png

openapi_btn_applynow.png

28 ms

openapi_btn_learnmore.png

openapi_btn_learnmore.png

30 ms

openapi_guide_bg.png

openapi_guide_bg.png

30 ms

openapi_icon_provided_hover.png

openapi_icon_provided_hover.png

34 ms

openapi_icon_how.png

openapi_icon_how.png

36 ms

openapi_icon_supported.png

openapi_icon_supported.png

46 ms

openapi_icon_process.png

openapi_icon_process.png

42 ms

openapi_home_pic2.png

openapi_home_pic2.png

48 ms

openapi_home_pic1.png

openapi_home_pic1.png

46 ms

openapi_home_pic6_en.png

openapi_home_pic6_en.png

49 ms

openapi_home_pic5_en.png

openapi_home_pic5_en.png

54 ms

openapi_home_pic3.png

openapi_home_pic3.png

55 ms

openapi_home_pic4.png

openapi_home_pic4.png

60 ms

openapi_footer.png

openapi_footer.png

61 ms

openapi_footer_triangle.png

openapi_footer_triangle.png

61 ms

foot_icons.png

foot_icons.png

64 ms

openapi_google.png

openapi_google.png

70 ms

Accessibility Review

dev.camscanner.com accessibility score

64

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.

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

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

Links do not have a discernible name

Best Practices

dev.camscanner.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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dev.camscanner.com SEO score

67

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

dev.camscanner.com

Open Graph data is detected on the main page of Dev Cam Scanner. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: