Tools & Wizards About Us
indabox.it screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

indabox.it

IndaBox | Punti di ritiro e spedizione pacchi

Page Load Speed

5 sec in total

First Response

699 ms

Resources Loaded

3.9 sec

Page Rendered

472 ms

indabox.it screenshot

About Website

Welcome to indabox.it homepage info - get ready to check Inda Box best content for Italy right away, or after learning these important things about indabox.it

La rete di oltre 10.000 punti di ritiro pacchi per ricevere acquisti o spedire pacchi online. Spedizioni nazionali e internazionali.

Visit indabox.it

Key Findings

We analyzed Indabox.it page load time and found that the first response time was 699 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

indabox.it performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.25

50/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

indabox.it

699 ms

www.indabox.it

1503 ms

style.css

335 ms

css

67 ms

css

81 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 68% of them (68 requests) were addressed to the original Indabox.it, 6% (6 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Indabox.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (59%)

Content Size

2.1 MB

After Optimization

856.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indabox.it main page is 2.1 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. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 28.8 kB

  • Original 38.6 kB
  • After minification 34.8 kB
  • After compression 9.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. 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 28.8 kB or 75% of the original size.

Image Optimization

-18%

Potential reduce by 93.1 kB

  • Original 510.7 kB
  • After minification 417.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, Inda Box needs image optimization as it can save up to 93.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 682.9 kB

  • Original 1.0 MB
  • After minification 985.6 kB
  • After compression 344.7 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 682.9 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 419.0 kB

  • Original 503.0 kB
  • After minification 464.8 kB
  • After compression 84.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. Indabox.it needs all CSS files to be minified and compressed as it can save up to 419.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (47%)

Requests Now

89

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indabox.it

indabox.it

699 ms

www.indabox.it

www.indabox.it

1503 ms

style.css

style.css

335 ms

css

css

67 ms

css

css

81 ms

jquery.min.js

jquery.min.js

500 ms

theme-my-login.css

theme-my-login.css

307 ms

font-awesome.min.css

font-awesome.min.css

315 ms

styles.css

styles.css

323 ms

cli-style.css

cli-style.css

324 ms

fancybox.css

fancybox.css

403 ms

frontend-uploader.css

frontend-uploader.css

420 ms

style.css

style.css

426 ms

thickbox.css

thickbox.css

428 ms

jquery.js

jquery.js

531 ms

jquery-migrate.min.js

jquery-migrate.min.js

521 ms

cookielawinfo.js

cookielawinfo.js

525 ms

jquery.validate.min.js

jquery.validate.min.js

144 ms

frontend-uploader.js

frontend-uploader.js

528 ms

messages_it.js

messages_it.js

177 ms

js

js

54 ms

autocomplete.js

autocomplete.js

528 ms

wp-activity.css

wp-activity.css

592 ms

conversion.js

conversion.js

65 ms

code.js

code.js

532 ms

jquery.form.min.js

jquery.form.min.js

621 ms

scripts.js

scripts.js

620 ms

jquery.fancybox.js

jquery.fancybox.js

620 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

624 ms

locate.js

locate.js

628 ms

thickbox.js

thickbox.js

630 ms

analytics.js

analytics.js

123 ms

gplus-16.png

gplus-16.png

179 ms

diagonal2.jpg

diagonal2.jpg

249 ms

barra.jpg

barra.jpg

249 ms

app_play_store.png

app_play_store.png

246 ms

app_store.png

app_store.png

247 ms

facebook.png

facebook.png

246 ms

arrow_up.png

arrow_up.png

281 ms

logo.png

logo.png

387 ms

logo_mobile.png

logo_mobile.png

388 ms

locate-me-blue.png

locate-me-blue.png

394 ms

yt-thumb.jpg

yt-thumb.jpg

664 ms

icons_video.png

icons_video.png

394 ms

icons_scopri.png

icons_scopri.png

395 ms

barit-300x140.jpg

barit-300x140.jpg

455 ms

crf_mkt_logo.png

crf_mkt_logo.png

539 ms

nestle-300x140.png

nestle-300x140.png

666 ms

reale-300x161.jpg

reale-300x161.jpg

459 ms

ausilium-e1412948916376.gif

ausilium-e1412948916376.gif

475 ms

bazzalia.png

bazzalia.png

551 ms

farma_sprint.jpg

farma_sprint.jpg

563 ms

spare_party.jpg

spare_party.jpg

669 ms

tesi24-e1415691963216.jpg

tesi24-e1415691963216.jpg

645 ms

bar1.png

bar1.png

649 ms

utente.png

utente.png

666 ms

cell.png

cell.png

734 ms

twitter.png

twitter.png

746 ms

loghino.png

loghino.png

765 ms

PayPal_logo_80x35.gif

PayPal_logo_80x35.gif

768 ms

partners_slide.png

partners_slide.png

859 ms

search1.png

search1.png

752 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

207 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

225 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

246 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

259 ms

common.js

common.js

123 ms

util.js

util.js

152 ms

controls.js

controls.js

140 ms

places_impl.js

places_impl.js

139 ms

p0Wc2yQVvz4

p0Wc2yQVvz4

210 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

968 ms

160 ms

fbds.js

fbds.js

283 ms

landing_attesa.png

landing_attesa.png

737 ms

landing_avviso.png

landing_avviso.png

760 ms

landing_suocera.png

landing_suocera.png

754 ms

landing_coda.png

landing_coda.png

761 ms

noise2.jpg

noise2.jpg

785 ms

collect

collect

33 ms

icons_trova.png

icons_trova.png

794 ms

collect

collect

120 ms

powered-by-google-on-white3.png

powered-by-google-on-white3.png

99 ms

autocomplete-icons.png

autocomplete-icons.png

156 ms

icons_compra.png

icons_compra.png

734 ms

icons_segnala.png

icons_segnala.png

738 ms

icons_ritira.png

icons_ritira.png

736 ms

dicono2.png

dicono2.png

891 ms

noise_green.jpg

noise_green.jpg

807 ms

126 ms

www-embed-player-vflQrT_sR.css

www-embed-player-vflQrT_sR.css

68 ms

www-embed-player.js

www-embed-player.js

89 ms

overlay.png

overlay.png

791 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

17 ms

ad_status.js

ad_status.js

86 ms

loadingAnimation.gif

loadingAnimation.gif

699 ms

121 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

10 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

8 ms

20 ms

Accessibility Review

indabox.it accessibility score

67

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

indabox.it best practices score

83

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

Page has valid source maps

SEO Factors

indabox.it SEO score

83

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

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

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

indabox.it

Open Graph data is detected on the main page of Inda Box. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: