1.8 sec in total
77 ms
1.5 sec
189 ms
Visit puckerfish.net now to see the best up-to-date Puckerfish content and also check out these interesting facts you probably never knew about puckerfish.net
Puckerfish, LLC, in Mansfield, OH, offers high quality custom e-juice flavors and electronic cigarettes. Our vaporizors and e-cigarettes have all interchangeable parts and our e-liquids have a bold ...
Visit puckerfish.netWe analyzed Puckerfish.net page load time and found that the first response time was 77 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
puckerfish.net performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value3.7 s
58/100
25%
Value8.2 s
20/100
10%
Value10,830 ms
0/100
30%
Value0
100/100
15%
Value17.7 s
4/100
10%
77 ms
100 ms
39 ms
196 ms
121 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 18% of them (13 requests) were addressed to the original Puckerfish.net, 50% (37 requests) were made to Maps.google.com and 14% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (196 ms) belongs to the original domain Puckerfish.net.
Page size can be reduced by 501.9 kB (37%)
1.4 MB
852.7 kB
In fact, the total size of Puckerfish.net main page is 1.4 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 641.8 kB which makes up the majority of the site volume.
Potential reduce by 39.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 39.8 kB or 83% of the original size.
Potential reduce by 19.7 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. Puckerfish images are well optimized though.
Potential reduce by 422.2 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 422.2 kB or 66% of the original size.
Potential reduce by 20.2 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. Puckerfish.net needs all CSS files to be minified and compressed as it can save up to 20.2 kB or 81% of the original size.
Number of requests can be reduced by 22 (34%)
65
43
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puckerfish. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
puckerfish.net
77 ms
www.puckerfish.net
100 ms
main.css
39 ms
jquery-1.9.1.min.js
196 ms
jquery.fancybox.pack.js
121 ms
jquery.fancybox.css
79 ms
app.js
107 ms
scripts.js
103 ms
jquery-1.9.0.min.js
7 ms
js
22 ms
css
23 ms
analytics.js
34 ms
mainBackground.jpg
76 ms
headerBackground.jpg
41 ms
puckerFishLogo.png
60 ms
contentGradient.png
60 ms
ashland-storefront.jpg
152 ms
DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff
10 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
12 ms
MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff
15 ms
collect
13 ms
common.js
5 ms
map.js
18 ms
util.js
17 ms
marker.js
17 ms
infowindow.js
15 ms
onion.js
27 ms
openhand_8_8.cur
20 ms
css
22 ms
transparent.png
18 ms
ViewportInfoService.GetViewportInfo
84 ms
stats.js
12 ms
controls.js
9 ms
mapcnt6.png
41 ms
google4.png
21 ms
sv5.png
20 ms
spotlight-poi.png
20 ms
d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff
13 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
13 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
13 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
13 ms
tmapctrl.png
34 ms
cb_scout5.png
34 ms
tmapctrl4.png
35 ms
imgs8.png
34 ms
vt
10 ms
vt
24 ms
vt
7 ms
vt
9 ms
vt
8 ms
vt
8 ms
vt
10 ms
vt
13 ms
vt
9 ms
vt
10 ms
vt
11 ms
vt
12 ms
vt
14 ms
vt
13 ms
vt
13 ms
vt
14 ms
AuthenticationService.Authenticate
153 ms
vt
4 ms
vt
6 ms
vt
4 ms
vt
6 ms
vt
4 ms
vt
45 ms
vt
9 ms
vt
5 ms
vt
7 ms
vt
9 ms
vt
9 ms
vt
15 ms
puckerfish.net accessibility score
puckerfish.net 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
puckerfish.net SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puckerfish.net 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 Puckerfish.net 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.
puckerfish.net
Open Graph description is not detected on the main page of Puckerfish. 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: