Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 0

    Best Practices

  • 75

    SEO

    Google-friendlier than
    32% of websites

dotwise.uk

SEO, PPC, Web Design | Digital Marketing Surrey,London | Dotwise

Page Load Speed

455 ms in total

First Response

28 ms

Resources Loaded

375 ms

Page Rendered

52 ms

dotwise.uk screenshot

About Website

Click here to check amazing Dotwise content. Otherwise, check out these important facts you probably never knew about dotwise.uk

Dotwise is an experienced digital marketing company in London, Surrey and across the UK. We specialise in SEO, PPC, Google Ads, web design and maintenance.

Visit dotwise.uk

Key Findings

We analyzed Dotwise.uk page load time and found that the first response time was 28 ms and then it took 427 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

dotwise.uk performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value1.3 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.319

36/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

dotwise.uk

28 ms

dotwise.uk

345 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Dotwise.uk and no external sources were called. The less responsive or slowest element that took the longest time to load (345 ms) belongs to the original domain Dotwise.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 177.4 kB (23%)

Content Size

774.6 kB

After Optimization

597.2 kB

In fact, the total size of Dotwise.uk main page is 774.6 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 624.7 kB which makes up the majority of the site volume.

HTML Optimization

-13%

Potential reduce by 23 B

  • Original 177 B
  • After minification 177 B
  • After compression 154 B

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 23 B or 13% of the original size.

Image Optimization

-25%

Potential reduce by 155.6 kB

  • Original 624.7 kB
  • After minification 469.1 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. Obviously, Dotwise needs image optimization as it can save up to 155.6 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 1.8 kB

  • Original 89.4 kB
  • After minification 89.4 kB
  • After compression 87.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. This website has mostly compressed JavaScripts.

CSS Optimization

-33%

Potential reduce by 19.9 kB

  • Original 60.3 kB
  • After minification 60.3 kB
  • After compression 40.4 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. Dotwise.uk needs all CSS files to be minified and compressed as it can save up to 19.9 kB or 33% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

dotwise.uk accessibility score

84

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

Document doesn't have a <title> element

SEO Factors

dotwise.uk SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dotwise.uk 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 Dotwise.uk main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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