Tools & Wizards About Us
greenprintqatar.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

greenprintqatar.com

Green Print WLL | Printing Press in Qatar | Offset Printing Press Qatar, Digital Printing Qatar

Page Load Speed

2.1 sec in total

First Response

220 ms

Resources Loaded

1.6 sec

Page Rendered

291 ms

greenprintqatar.com screenshot

About Website

Click here to check amazing Green Print Qatar content. Otherwise, check out these important facts you probably never knew about greenprintqatar.com

We are one of the leading printing press company in Qatar with complete printing solution. For more details call 44412120

Visit greenprintqatar.com

Key Findings

We analyzed Greenprintqatar.com page load time and found that the first response time was 220 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

greenprintqatar.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value29.1 s

0/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.186

65/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

greenprintqatar.com

220 ms

style.css

68 ms

font-awesome.min.css

126 ms

css

37 ms

css

55 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 74% of them (89 requests) were addressed to the original Greenprintqatar.com, 10% (12 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (696 ms) belongs to the original domain Greenprintqatar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.4 MB (54%)

Content Size

8.3 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greenprintqatar.com main page is 8.3 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. Only a small number of websites need less resources to load. Images take 7.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 49.7 kB

  • Original 60.5 kB
  • After minification 48.3 kB
  • After compression 10.8 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 12.2 kB, which is 20% 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 49.7 kB or 82% of the original size.

Image Optimization

-53%

Potential reduce by 4.1 MB

  • Original 7.7 MB
  • After minification 3.6 MB

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, Green Print Qatar needs image optimization as it can save up to 4.1 MB or 53% 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 266.5 kB

  • Original 515.4 kB
  • After minification 515.0 kB
  • After compression 249.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 266.5 kB or 52% of the original size.

CSS Optimization

-30%

Potential reduce by 5.5 kB

  • Original 18.1 kB
  • After minification 18.1 kB
  • After compression 12.6 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. Greenprintqatar.com needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (22%)

Requests Now

104

After Optimization

81

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greenprintqatar.com

greenprintqatar.com

220 ms

style.css

style.css

68 ms

font-awesome.min.css

font-awesome.min.css

126 ms

css

css

37 ms

css

css

55 ms

css

css

58 ms

css

css

60 ms

owl.carousel.css

owl.carousel.css

124 ms

owl.theme.css

owl.theme.css

123 ms

jquery.js

jquery.js

322 ms

plugin.js

plugin.js

186 ms

owl.carousel.js

owl.carousel.js

149 ms

js

js

71 ms

jqBootstrapValidation.js

jqBootstrapValidation.js

189 ms

contact_me.js

contact_me.js

187 ms

custom.js

custom.js

194 ms

xfbml.customerchat.js

xfbml.customerchat.js

32 ms

embed

embed

190 ms

logo.png

logo.png

70 ms

offset-printing.png

offset-printing.png

387 ms

digital-printing.png

digital-printing.png

469 ms

exhibition-stands.png

exhibition-stands.png

462 ms

corporate-gift-articles.png

corporate-gift-articles.png

386 ms

pu-leather.png

pu-leather.png

268 ms

screen-printing.png

screen-printing.png

347 ms

premium-packing.png

premium-packing.png

346 ms

print.png

print.png

466 ms

mc.png

mc.png

585 ms

GP-Structure.png

GP-Structure.png

468 ms

offset-print.png

offset-print.png

467 ms

digitalprint.png

digitalprint.png

538 ms

screen-print.png

screen-print.png

487 ms

PU-Leather.png

PU-Leather.png

504 ms

gift.png

gift.png

535 ms

stand.png

stand.png

535 ms

client%20(1).png

client%20(1).png

540 ms

client%20(2).png

client%20(2).png

583 ms

client%20(3).png

client%20(3).png

587 ms

client%20(4).png

client%20(4).png

586 ms

client%20(5).png

client%20(5).png

586 ms

client%20(6).png

client%20(6).png

603 ms

client%20(7).png

client%20(7).png

633 ms

client%20(8).png

client%20(8).png

633 ms

client%20(9).png

client%20(9).png

650 ms

client%20(10).png

client%20(10).png

649 ms

client%20(11).png

client%20(11).png

650 ms

client%20(12).png

client%20(12).png

666 ms

client%20(13).png

client%20(13).png

696 ms

client%20(14).png

client%20(14).png

694 ms

gtm.js

gtm.js

72 ms

client%20(15).png

client%20(15).png

674 ms

client%20(16).png

client%20(16).png

673 ms

client%20(17).png

client%20(17).png

672 ms

client%20(18).png

client%20(18).png

682 ms

js

js

73 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

577 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

79 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

98 ms

analytics.js

analytics.js

143 ms

260 ms

332 ms

webfont.js

webfont.js

85 ms

search.js

search.js

46 ms

geometry.js

geometry.js

80 ms

main.js

main.js

81 ms

client%20(20).png

client%20(20).png

498 ms

css

css

52 ms

client%20(21).png

client%20(21).png

421 ms

client%20(22).png

client%20(22).png

444 ms

collect

collect

86 ms

client%20(23).png

client%20(23).png

420 ms

client%20(24).png

client%20(24).png

361 ms

js

js

72 ms

client%20(25).png

client%20(25).png

359 ms

client%20(26).png

client%20(26).png

373 ms

client%20(27).png

client%20(27).png

370 ms

client%20(28).png

client%20(28).png

371 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

18 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

19 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

48 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

21 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

46 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

48 ms

client%20(29).png

client%20(29).png

384 ms

client%20(30).png

client%20(30).png

397 ms

client%20(31).png

client%20(31).png

380 ms

client%20(32).png

client%20(32).png

365 ms

client%20(33).png

client%20(33).png

366 ms

client%20(34).png

client%20(34).png

362 ms

client%20(35).png

client%20(35).png

349 ms

client%20(36).png

client%20(36).png

378 ms

client%20(37).png

client%20(37).png

377 ms

client%20(38).png

client%20(38).png

377 ms

client%20(39).png

client%20(39).png

399 ms

client%20(40).png

client%20(40).png

383 ms

client%20(41).png

client%20(41).png

383 ms

client%20(42).png

client%20(42).png

383 ms

client%20(43).png

client%20(43).png

382 ms

client%20(44).png

client%20(44).png

382 ms

client%20(45).png

client%20(45).png

382 ms

client%20(46).png

client%20(46).png

367 ms

client%20(47).png

client%20(47).png

397 ms

client%20(48).png

client%20(48).png

400 ms

client%20(49).png

client%20(49).png

382 ms

client%20(50).png

client%20(50).png

382 ms

client%20(51).png

client%20(51).png

381 ms

client%20(52).png

client%20(52).png

367 ms

client%20(53).png

client%20(53).png

392 ms

client%20(54).png

client%20(54).png

391 ms

client%20(55).png

client%20(55).png

392 ms

client%20(56).png

client%20(56).png

391 ms

client%20(57).png

client%20(57).png

384 ms

facebook.png

facebook.png

353 ms

twitter.png

twitter.png

383 ms

linkedin.png

linkedin.png

397 ms

instagram.png

instagram.png

383 ms

Accessibility Review

greenprintqatar.com accessibility score

84

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

greenprintqatar.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

greenprintqatar.com SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenprintqatar.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 Greenprintqatar.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

greenprintqatar.com

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