Tools & Wizards About Us
pack.ly screenshot

Report Summary

  • 0

    Performance

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 0

    Best Practices

  • 86

    SEO

    Google-friendlier than
    60% of websites

pack.ly

Create online custom printed packaging, dielines and 3Ds

Page Load Speed

4.7 sec in total

First Response

263 ms

Resources Loaded

3.7 sec

Page Rendered

726 ms

pack.ly screenshot

About Website

Welcome to pack.ly homepage info - get ready to check Pack best content for India right away, or after learning these important things about pack.ly

Create custom packaging online. No minimum quantity requirement. Generate the die-cut template with personalised sizes, view the real-time 3D, and get printed custom boxes in 48h.

Visit pack.ly

Key Findings

We analyzed Pack.ly page load time and found that the first response time was 263 ms and then it took 4.4 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

pack.ly performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value49.6 s

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value45,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value91.0 s

0/100

10%

Network Requests Diagram

pack.ly

263 ms

www.pack.ly

384 ms

en

381 ms

MepzaKM12bzc-mXjn23EXR9xASE.js

31 ms

landing.css

241 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 40% of them (21 requests) were addressed to the original Pack.ly, 10% (5 requests) were made to Cdn.iubenda.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (857 ms) relates to the external source Rum-static.pingdom.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 226.5 kB (31%)

Content Size

723.2 kB

After Optimization

496.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pack.ly main page is 723.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 480.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 171.9 kB

  • Original 198.0 kB
  • After minification 196.3 kB
  • After compression 26.1 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 171.9 kB or 87% of the original size.

Image Optimization

-11%

Potential reduce by 54.3 kB

  • Original 480.4 kB
  • After minification 426.1 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, Pack needs image optimization as it can save up to 54.3 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

-1%

Potential reduce by 241 B

  • Original 44.8 kB
  • After minification 44.8 kB
  • After compression 44.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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

42

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pack.ly

pack.ly

263 ms

www.pack.ly

www.pack.ly

384 ms

en

en

381 ms

MepzaKM12bzc-mXjn23EXR9xASE.js

MepzaKM12bzc-mXjn23EXR9xASE.js

31 ms

landing.css

landing.css

241 ms

icon

icon

82 ms

css

css

124 ms

webcomponents

webcomponents

220 ms

jquery.js

jquery.js

214 ms

materialize.js

materialize.js

216 ms

vendor.js

vendor.js

227 ms

landing.js

landing.js

215 ms

analytics.js

analytics.js

107 ms

collect

collect

570 ms

gtm.js

gtm.js

580 ms

bg-sidenav-blue.jpg

bg-sidenav-blue.jpg

450 ms

bg-sidenav-green.jpg

bg-sidenav-green.jpg

446 ms

cover-hero-lidAndBottom.png

cover-hero-lidAndBottom.png

467 ms

check-bold.svg

check-bold.svg

444 ms

3cf6adf61054c328b1b0ddcd8f9ce24d.woff

3cf6adf61054c328b1b0ddcd8f9ce24d.woff

347 ms

cf4d60bc0b1d4b2314085919a00e1724.woff

cf4d60bc0b1d4b2314085919a00e1724.woff

347 ms

ea36cd9a0e9eee97012a67b8a4570d7b.woff

ea36cd9a0e9eee97012a67b8a4570d7b.woff

551 ms

44b78f142603eb69f593ed4002ed7a4a.woff

44b78f142603eb69f593ed4002ed7a4a.woff

552 ms

eed9aab5449cc9c8430d7d258108f602.woff

eed9aab5449cc9c8430d7d258108f602.woff

551 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

346 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNaIhQ8tQ.woff

flUhRq6tzZclQEJ-Vdg-IuiaDsNaIhQ8tQ.woff

353 ms

invisible.js

invisible.js

164 ms

collect

collect

258 ms

die-cut-illustration.png

die-cut-illustration.png

344 ms

ga-audiences

ga-audiences

352 ms

hotjar-2908438.js

hotjar-2908438.js

568 ms

conversion_async.js

conversion_async.js

456 ms

collect

collect

250 ms

insight.min.js

insight.min.js

472 ms

pa-5ca1e9c7cea07b00160010af.js

pa-5ca1e9c7cea07b00160010af.js

857 ms

fbevents.js

fbevents.js

433 ms

stub.js

stub.js

492 ms

iubenda_cons.js

iubenda_cons.js

492 ms

js

js

281 ms

75409efe9f7e6fe6

75409efe9f7e6fe6

185 ms

collect

collect

183 ms

175 ms

ga-audiences

ga-audiences

51 ms

2298098023770660

2298098023770660

132 ms

modules.61e17720cf639c3e96a7.js

modules.61e17720cf639c3e96a7.js

252 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

200 ms

165 ms

iubenda_cs.js

iubenda_cs.js

31 ms

core-8fdcb29dc2a89f2172df78c5f7cb048f.js

core-8fdcb29dc2a89f2172df78c5f7cb048f.js

31 ms

core-en-GB.js

core-en-GB.js

42 ms

78914273.js

78914273.js

218 ms

16 ms

Accessibility Review

pack.ly accessibility score

88

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

SEO Factors

pack.ly SEO score

86

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

Links do not have descriptive text

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 Pack.ly 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 Pack.ly 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

pack.ly

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