1.1 sec in total
145 ms
755 ms
234 ms
Welcome to prankpack.com homepage info - get ready to check Prank Pack best content for United States right away, or after learning these important things about prankpack.com
Looking for a unique baby shower gift box or the ideal stocking stuffer? Prank-O offers the best gag gifts to make any occasion more memorable. Browse our selection today!
Visit prankpack.comWe analyzed Prankpack.com page load time and found that the first response time was 145 ms and then it took 989 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
prankpack.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value12.5 s
0/100
25%
Value9.0 s
14/100
10%
Value2,140 ms
6/100
30%
Value0.131
81/100
15%
Value19.9 s
2/100
10%
145 ms
28 ms
44 ms
29 ms
26 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Prankpack.com, 60% (30 requests) were made to Cdn.shopify.com and 8% (4 requests) were made to Cdn.luckyorange.net. The less responsive or slowest element that took the longest time to load (305 ms) relates to the external source Cdn.secomapp.com.
Page size can be reduced by 430.5 kB (23%)
1.8 MB
1.4 MB
In fact, the total size of Prankpack.com main page is 1.8 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 36.4 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 7.4 kB, which is 17% 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 36.4 kB or 82% of the original size.
Potential reduce by 1.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. Prank Pack images are well optimized though.
Potential reduce by 305.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 305.0 kB or 66% of the original size.
Potential reduce by 87.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. Prankpack.com needs all CSS files to be minified and compressed as it can save up to 87.6 kB or 75% of the original size.
Number of requests can be reduced by 27 (56%)
48
21
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prank 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 22 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
prankpack.com
145 ms
ajaxify.scss.css
28 ms
timber.scss.css
44 ms
theme.scss.css
29 ms
css
26 ms
ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js
21 ms
jquery.min.js
31 ms
modernizr.min.js
24 ms
sca.freegift.css
38 ms
jquery.flexslider.min.js
25 ms
slider.js
20 ms
fastclick.min.js
22 ms
timber.js
24 ms
theme.js
67 ms
handlebars.min.js
72 ms
ajaxify.js
65 ms
shopify_stats.js
40 ms
analytics.js
40 ms
fbevents.js
87 ms
logo.png
77 ms
slide_1.jpg
75 ms
slide_2.jpg
75 ms
slide_3.jpg
74 ms
slide_5.jpg
80 ms
slide_6.jpg
77 ms
WebImage._0001s_0007_PP.3DHeros.Earwax.RightFace.HR.Batch2.png_large.jpg
82 ms
icon-freegift.png
80 ms
PP.3DHeros.Froogal.RightFace.HR.Batch2_large.png
81 ms
PP.3DHeros.Earwax.RightFace.HR.Batch1.png_copy_large.jpg
88 ms
WebImage._0001s_0000_PP.3DHeros.AuroSauna.RightFace.HR.Batch2.png_large.jpg
85 ms
WebImage-1_0000_Crib_medium.jpg
82 ms
WebImage-1_0003_Bird_medium.jpg
83 ms
WebImage._0003s_0003_PP.3DHeros.Fruitcake.PP501005.png_medium.jpg
83 ms
WebImage-1_0001_Cheap_medium.jpg
83 ms
collect
22 ms
icons.woff
22 ms
102 ms
record.gif
74 ms
quantity_breaks.php
24 ms
w.js
22 ms
icf.js
59 ms
prank-pack.myshopify.com_1449679169.js
305 ms
clickstream.min.js
15 ms
json.get_site_id_from_domain.php
12 ms
storage.luckyorange.net
90 ms
settings.luckyorange.net
91 ms
44 ms
mutation.min.js
9 ms
reset.css
36 ms
magnific-popup.min.css
25 ms
prankpack.com accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
prankpack.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
prankpack.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prankpack.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 Prankpack.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.
prankpack.com
Open Graph data is detected on the main page of Prank Pack. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: