Tools & Wizards About Us
lizarc.com screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

lizarc.com

REZA KALANTAR

Page Load Speed

2.5 sec in total

First Response

373 ms

Resources Loaded

1.9 sec

Page Rendered

180 ms

lizarc.com screenshot

About Website

Welcome to lizarc.com homepage info - get ready to check Lizarc best content right away, or after learning these important things about lizarc.com

BookCard - Responsive HTML5 vCard Template

Visit lizarc.com

Key Findings

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

lizarc.com performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value1.511

0/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

lizarc.com

373 ms

rez

415 ms

94 ms

modernizr.js

88 ms

css

20 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lizarc.com, 66% (50 requests) were made to Lizarcphotografix.co.uk and 24% (18 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (689 ms) relates to the external source Lizarcphotografix.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 279.8 kB (27%)

Content Size

1.0 MB

After Optimization

739.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-94%

Potential reduce by 113.8 kB

  • Original 121.0 kB
  • After minification 56.1 kB
  • After compression 7.2 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 64.8 kB, which is 54% 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 113.8 kB or 94% of the original size.

Image Optimization

-12%

Potential reduce by 87.1 kB

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

JavaScript Optimization

-52%

Potential reduce by 71.9 kB

  • Original 138.4 kB
  • After minification 125.7 kB
  • After compression 66.5 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 71.9 kB or 52% of the original size.

CSS Optimization

-21%

Potential reduce by 7.0 kB

  • Original 33.0 kB
  • After minification 32.7 kB
  • After compression 26.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. Lizarc.com needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (53%)

Requests Now

53

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lizarc.com

lizarc.com

373 ms

rez

rez

415 ms

94 ms

modernizr.js

modernizr.js

88 ms

css

css

20 ms

css

css

38 ms

css

css

39 ms

normalize.css

normalize.css

173 ms

bootstrap.min.css

bootstrap.min.css

173 ms

animate.css

animate.css

174 ms

book.css

book.css

171 ms

font-awesome.css

font-awesome.css

175 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

177 ms

main.css

main.css

342 ms

standart.css

standart.css

260 ms

clean.css

clean.css

259 ms

cream-dust.css

cream-dust.css

260 ms

linen.css

linen.css

259 ms

jquery.min.js

jquery.min.js

8 ms

jquery.address-1.5.min.js

jquery.address-1.5.min.js

259 ms

antiscroll.js

antiscroll.js

435 ms

jquery.fittext.js

jquery.fittext.js

433 ms

jquery.imagesloaded.min.js

jquery.imagesloaded.min.js

434 ms

jquery.isotope.min.js

jquery.isotope.min.js

435 ms

jquery.fitvids.js

jquery.fitvids.js

434 ms

jquery.validate.min.js

jquery.validate.min.js

436 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

513 ms

send-mail.js

send-mail.js

437 ms

twitterFetcher_v10_min.js

twitterFetcher_v10_min.js

435 ms

main.js

main.js

436 ms

embed

embed

215 ms

cover.jpg

cover.jpg

588 ms

testo-01.jpg

testo-01.jpg

414 ms

testo-02.jpg

testo-02.jpg

500 ms

testo-03.jpg

testo-03.jpg

500 ms

01.jpg

01.jpg

503 ms

02.jpg

02.jpg

498 ms

03.jpg

03.jpg

583 ms

04.jpg

04.jpg

585 ms

05.jpg

05.jpg

586 ms

06.jpg

06.jpg

587 ms

07.jpg

07.jpg

587 ms

08.jpg

08.jpg

668 ms

09.jpg

09.jpg

669 ms

cover-2.jpg

cover-2.jpg

671 ms

stamp-image.png

stamp-image.png

689 ms

loader_light.gif

loader_light.gif

609 ms

css

css

19 ms

js

js

123 ms

linen.png

linen.png

420 ms

cream_dust.png

cream_dust.png

496 ms

letter-lines.png

letter-lines.png

496 ms

stamp.png

stamp.png

498 ms

stamp-mask.png

stamp-mask.png

500 ms

loader_dark.gif

loader_dark.gif

501 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

13 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

7 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

13 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

13 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

32 ms

6NUQ8FmMKwSEKjnm5-4v-4Jh2dJhfg.ttf

6NUQ8FmMKwSEKjnm5-4v-4Jh2dJhfg.ttf

32 ms

lW-8wjkKLXjg5y2o2uUYV-t3.ttf

lW-8wjkKLXjg5y2o2uUYV-t3.ttf

31 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

32 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

33 ms

tDbM2oWUg0MKoZw1-LPK9g.ttf

tDbM2oWUg0MKoZw1-LPK9g.ttf

33 ms

tDbD2oWUg0MKqScQ6A.ttf

tDbD2oWUg0MKqScQ6A.ttf

34 ms

dFa6ZfeC474skLgesc0Cajo6-A.ttf

dFa6ZfeC474skLgesc0Cajo6-A.ttf

34 ms

S6u8w4BMUTPHjxsAXC-v.ttf

S6u8w4BMUTPHjxsAXC-v.ttf

33 ms

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

34 ms

S6u-w4BMUTPHjxsIPx-oPCc.ttf

S6u-w4BMUTPHjxsIPx-oPCc.ttf

34 ms

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

35 ms

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

35 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

500 ms

justvector-webfont.woff

justvector-webfont.woff

495 ms

buEzpo6gcdjy0EiZMBUG4C0f-A.ttf

buEzpo6gcdjy0EiZMBUG4C0f-A.ttf

35 ms

print.css

print.css

88 ms

Accessibility Review

lizarc.com accessibility score

80

Accessibility Issues

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

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

Browser errors were logged to the console

SEO Factors

lizarc.com SEO score

91

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

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

lizarc.com

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