Tools & Wizards About Us
clean-lines.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 0

    Best Practices

  • 93

    SEO

    Google-friendlier than
    83% of websites

clean-lines.com

Index of /

Page Load Speed

5.5 sec in total

First Response

1.3 sec

Resources Loaded

3.9 sec

Page Rendered

217 ms

clean-lines.com screenshot

About Website

Click here to check amazing Clean Lines content for Australia. Otherwise, check out these important facts you probably never knew about clean-lines.com

Clean Lines Web Development Byron Bay specialises in Joomla, Magento, Wordpress, Open-source CMS customisation SEO, online and social media marketing.

Visit clean-lines.com

Key Findings

We analyzed Clean-lines.com page load time and found that the first response time was 1.3 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

clean-lines.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value4,940 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.173

69/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

clean-lines.com

1341 ms

ga.js

26 ms

wp-emoji-release.min.js

115 ms

style.css

224 ms

css

27 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 84% of them (62 requests) were addressed to the original Clean-lines.com, 5% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Clean-lines.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (80%)

Content Size

2.7 MB

After Optimization

546.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Clean-lines.com main page is 2.7 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. 45% of websites need less resources to load. CSS take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 84.6 kB

  • Original 104.5 kB
  • After minification 101.2 kB
  • After compression 19.9 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 84.6 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 15.7 kB

  • Original 147.3 kB
  • After minification 131.6 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, Clean Lines needs image optimization as it can save up to 15.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 608.4 kB

  • Original 845.3 kB
  • After minification 786.5 kB
  • After compression 236.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 608.4 kB or 72% of the original size.

CSS Optimization

-90%

Potential reduce by 1.5 MB

  • Original 1.6 MB
  • After minification 1.5 MB
  • After compression 157.7 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. Clean-lines.com needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (64%)

Requests Now

67

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

clean-lines.com

clean-lines.com

1341 ms

ga.js

ga.js

26 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

115 ms

style.css

style.css

224 ms

css

css

27 ms

style.css

style.css

141 ms

styles.css

styles.css

156 ms

css

css

39 ms

css3_grid_style.css

css3_grid_style.css

298 ms

css3_grid_style.css

css3_grid_style.css

370 ms

responsive.css

responsive.css

216 ms

settings.css

settings.css

328 ms

load-posts.css

load-posts.css

296 ms

css

css

43 ms

js_composer.min.css

js_composer.min.css

661 ms

skeleton.css

skeleton.css

384 ms

camera.css

camera.css

409 ms

skin.css

skin.css

480 ms

flexslider.css

flexslider.css

444 ms

blog.css

blog.css

487 ms

prettyPhoto.css

prettyPhoto.css

491 ms

resize.css

resize.css

560 ms

font-awesome.min.css

font-awesome.min.css

557 ms

retina.css

retina.css

592 ms

animate.css

animate.css

694 ms

component.css

component.css

634 ms

editor-style.css

editor-style.css

633 ms

jquery.js

jquery.js

746 ms

jquery-migrate.min.js

jquery-migrate.min.js

695 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

815 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

819 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

734 ms

blog.js

blog.js

778 ms

__utm.gif

__utm.gif

11 ms

comment-reply.min.js

comment-reply.min.js

514 ms

jquery.form.min.js

jquery.form.min.js

577 ms

scripts.js

scripts.js

587 ms

jQuerytools.js

jQuerytools.js

590 ms

utils.js

utils.js

802 ms

waypoints.min.js

waypoints.min.js

652 ms

animated-contents.js

animated-contents.js

691 ms

jquery.fitvids.js

jquery.fitvids.js

660 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

662 ms

smartbox.js

smartbox.js

810 ms

jquery.tweet.js

jquery.tweet.js

729 ms

js_composer_front.js

js_composer_front.js

771 ms

shortcodes.css

shortcodes.css

416 ms

1392784531logo-lar32.png

1392784531logo-lar32.png

421 ms

frog.jpg

frog.jpg

139 ms

sprite.png

sprite.png

138 ms

transparent.png

transparent.png

95 ms

bali-accom-logo.gif

bali-accom-logo.gif

95 ms

bodypeace-thu.gif

bodypeace-thu.gif

96 ms

bbd-logo-thumb.jpg

bbd-logo-thumb.jpg

414 ms

civil-thu.gif

civil-thu.gif

138 ms

ajx_loading.gif

ajx_loading.gif

414 ms

1392784317logo32.png

1392784317logo32.png

417 ms

home-logo-wordpress.png

home-logo-wordpress.png

417 ms

home-logo-magento.png

home-logo-magento.png

418 ms

home-logo-joomla.png

home-logo-joomla.png

419 ms

home-logo-drupal.png

home-logo-drupal.png

419 ms

penguin.jpg

penguin.jpg

413 ms

fishjpg.jpg

fishjpg.jpg

414 ms

header-shadow.png

header-shadow.png

406 ms

MG9KbUZFchDs94Tbv9U-pT8E0i7KZn-EPnyo3HZu7kw.woff

MG9KbUZFchDs94Tbv9U-pT8E0i7KZn-EPnyo3HZu7kw.woff

19 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

360 ms

twitter_bird.png

twitter_bird.png

286 ms

OpenSans-Bold-webfont.woff

OpenSans-Bold-webfont.woff

276 ms

loading.gif

loading.gif

166 ms

large_left.png

large_left.png

92 ms

large_right.png

large_right.png

92 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

13 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

12 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

13 ms

Accessibility Review

clean-lines.com accessibility score

54

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

SEO Factors

clean-lines.com SEO score

93

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

clean-lines.com

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