Tools & Wizards About Us
qima-produce.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

qima-produce.com

Produce Inspections, Audits and Testing | QIMA - Produce Quality Control

Page Load Speed

2.4 sec in total

First Response

73 ms

Resources Loaded

1.7 sec

Page Rendered

634 ms

qima-produce.com screenshot

About Website

Visit qima-produce.com now to see the best up-to-date QIMA Produce content and also check out these interesting facts you probably never knew about qima-produce.com

QIMA offers accurate and reliable product inspections for produce, helping you ensure quality and safety at every stage of your supply chain

Visit qima-produce.com

Key Findings

We analyzed Qima-produce.com page load time and found that the first response time was 73 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

qima-produce.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

qima-produce.com

73 ms

www.qima-produce.com

60 ms

fresh-produce

3 ms

fresh-produce

118 ms

uc.js

145 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 21% of them (13 requests) were addressed to the original Qima-produce.com, 44% (27 requests) were made to S3.qima.com and 3% (2 requests) were made to Munchkin.marketo.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Unpkg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.5 kB (10%)

Content Size

2.3 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qima-produce.com main page is 2.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. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 83.4 kB

  • Original 109.2 kB
  • After minification 89.0 kB
  • After compression 25.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 20.2 kB, which is 19% 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 83.4 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 106.8 kB

  • Original 1.3 MB
  • After minification 1.2 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. QIMA Produce images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 26.8 kB

  • Original 764.6 kB
  • After minification 764.3 kB
  • After compression 737.8 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

-2%

Potential reduce by 1.5 kB

  • Original 64.8 kB
  • After minification 64.8 kB
  • After compression 63.3 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. Qima-produce.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (55%)

Requests Now

55

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qima-produce.com

qima-produce.com

73 ms

www.qima-produce.com

www.qima-produce.com

60 ms

fresh-produce

fresh-produce

3 ms

fresh-produce

fresh-produce

118 ms

uc.js

uc.js

145 ms

stimg.js

stimg.js

219 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

180 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

169 ms

jquery-migrate-1.4.1.min.js

jquery-migrate-1.4.1.min.js

180 ms

head.js

head.js

13 ms

c9aa759.css

c9aa759.css

82 ms

c42b74e.css

c42b74e.css

98 ms

autoComplete.min.css

autoComplete.min.css

367 ms

wistia-v1.js

wistia-v1.js

139 ms

api.js

api.js

356 ms

vendor.js

vendor.js

181 ms

autofill.js

autofill.js

86 ms

2b6fd93.js

2b6fd93.js

168 ms

autoComplete.min.js

autoComplete.min.js

448 ms

s_code.js

s_code.js

158 ms

conversion.js

conversion.js

346 ms

oct.js

oct.js

233 ms

stimg.rgjhmhlh.js

stimg.rgjhmhlh.js

1213 ms

gtm.js

gtm.js

425 ms

fbt.js

fbt.js

414 ms

qima%402x.png

qima%402x.png

144 ms

qima-play-sm.png

qima-play-sm.png

249 ms

produce_ico1.png

produce_ico1.png

357 ms

produce_ico2.png

produce_ico2.png

268 ms

produce_ico3.png

produce_ico3.png

267 ms

produce_ico4.png

produce_ico4.png

247 ms

produce_ico5.png

produce_ico5.png

290 ms

produce_ico6.png

produce_ico6.png

289 ms

produce_ico7.png

produce_ico7.png

288 ms

grower.png

grower.png

291 ms

exporter.png

exporter.png

290 ms

shipping.png

shipping.png

365 ms

importer.png

importer.png

307 ms

retailer.png

retailer.png

316 ms

fruits1_[lg].jpg

fruits1_[lg].jpg

268 ms

qc_left_img.png

qc_left_img.png

299 ms

report_left_IMG.jpg

report_left_IMG.jpg

272 ms

produce_about_BG.jpg

produce_about_BG.jpg

392 ms

tic.gif

tic.gif

285 ms

Wechat_app%20icon.png

Wechat_app%20icon.png

290 ms

recaptcha__en.js

recaptcha__en.js

267 ms

GothamRoundedBook_21018.ttf

GothamRoundedBook_21018.ttf

126 ms

GothamRoundedBold_21016.ttf

GothamRoundedBold_21016.ttf

147 ms

fieldarrow.png

fieldarrow.png

235 ms

ico_whatsapp.png

ico_whatsapp.png

231 ms

sprite_global.png

sprite_global.png

340 ms

ico_instagram_web.png

ico_instagram_web.png

233 ms

munchkin.js

munchkin.js

311 ms

169 ms

insight.min.js

insight.min.js

177 ms

loadingAnimation.gif

loadingAnimation.gif

146 ms

adsct

adsct

212 ms

adsct

adsct

239 ms

82 ms

s92239544796757

s92239544796757

77 ms

munchkin.js

munchkin.js

72 ms

visitWebPage

visitWebPage

28 ms

Accessibility Review

qima-produce.com accessibility score

75

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.

Best Practices

qima-produce.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

High

Missing source maps for large first-party JavaScript

SEO Factors

qima-produce.com SEO score

85

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

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

High

Tap targets are not sized appropriately

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 Qima-produce.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 Qima-produce.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

qima-produce.com

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