27.6 sec in total
73 ms
4.8 sec
22.7 sec
Visit johnjohn-florence.com now to see the best up-to-date Johnjohn Florence content and also check out these interesting facts you probably never knew about johnjohn-florence.com
Find your next surf trip with SwellPirate ✈️
Visit johnjohn-florence.comWe analyzed Johnjohn-florence.com page load time and found that the first response time was 73 ms and then it took 27.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
johnjohn-florence.com performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value8.2 s
2/100
25%
Value9.0 s
14/100
10%
Value350 ms
73/100
30%
Value0.005
100/100
15%
Value8.1 s
41/100
10%
73 ms
961 ms
41 ms
36 ms
45 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Johnjohn-florence.com, 85% (105 requests) were made to Firebasestorage.googleapis.com and 11% (13 requests) were made to Swellpirate.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Firebasestorage.googleapis.com.
Page size can be reduced by 1.8 MB (8%)
24.0 MB
22.2 MB
In fact, the total size of Johnjohn-florence.com main page is 24.0 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. 80% 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 22.6 MB which makes up the majority of the site volume.
Potential reduce by 1.2 MB
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 1.2 MB or 85% of the original size.
Potential reduce by 599.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. Johnjohn Florence images are well optimized though.
Number of requests can be reduced by 7 (6%)
121
114
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Johnjohn Florence. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
johnjohn-florence.com
73 ms
swellpirate.com
961 ms
mapbox-gl.css
41 ms
mapbox-gl-geocoder.css
36 ms
mapbox-gl.js
45 ms
mapbox-gl-geocoder.min.js
40 ms
entry.fd2c49f9.css
29 ms
TheNavbar.a937a306.css
118 ms
entry.7f6438cf.js
197 ms
home-hero-image.jpg
492 ms
sp-pirate-color.5f7a0536.svg
23 ms
sp-logo.232486d7.svg
25 ms
wave.a44bb5de.svg
29 ms
locationImages%2FsteamerLane.jpg
471 ms
locationImages%2Frincon.jpg
463 ms
locationImages%2Fwaikiki.jpg
468 ms
locationImages%2FcannonBeach.jpg
478 ms
locationImages%2FhanaleiBay.jpg
433 ms
locationImages%2Fpipeline.jpg
691 ms
locationImages%2FcoxBay.jpg
619 ms
locationImages%2Fmagics.jpg
654 ms
locationImages%2FhonoluaBay.jpg
679 ms
locationImages%2Fcolegio.jpg
662 ms
locationImages%2FmargaretRiver.jpg
731 ms
locationImages%2Fteahupoo.jpg
800 ms
locationImages%2Fballybunion.jpg
943 ms
locationImages%2Fpichilemu.jpg
903 ms
locationImages%2FshipsternBluff.jpg
838 ms
locationImages%2Fsupertubos.jpg
938 ms
locationImages%2FplayaDeTraba.jpg
920 ms
locationImages%2FsantaClara.jpg
1046 ms
locationImages%2FanchorPoint.jpg
1068 ms
locationImages%2FlaTorche.jpg
1082 ms
locationImages%2FlaIsla.jpg
1101 ms
locationImages%2Fsandvik.jpg
1124 ms
locationImages%2FjeffreysBay.jpg
1165 ms
locationImages%2Fhossegor.jpg
1197 ms
locationImages%2Fkommetjie.jpg
1239 ms
locationImages%2FsanSebastian.jpg
1332 ms
locationImages%2Fyakutat.jpg
1312 ms
locationImages%2Fcanoa.jpg
1324 ms
locationImages%2FnorthFistral.jpg
1364 ms
locationImages%2Ftonel.jpg
1377 ms
locationImages%2FelHierro.jpg
1441 ms
locationImages%2FpontaPreta.jpg
1460 ms
locationImages%2Fuluwatu.jpg
1529 ms
locationImages%2Fsouillac.webp
1506 ms
locationImages%2FblacksBeach.jpg
1554 ms
sp-pirate-black.6a646af8.svg
13 ms
blank.9219e0ff.js
5 ms
default.dff13de9.js
4 ms
sp-pirate-color.5f7a0536.svg
46 ms
sp-logo.232486d7.svg
7 ms
wave.a44bb5de.svg
6 ms
locationImages%2Flibanona.jpg
1099 ms
locationImages%2FlowerTrestles.jpg
1211 ms
locationImages%2Fvivier.jpg
1148 ms
locationImages%2Flacanau.jpg
1233 ms
locationImages%2Fmonuments.jpg
1201 ms
locationImages%2FbellsBeach.jpg
1186 ms
locationImages%2Fmacaronis.jpg
1088 ms
locationImages%2Fwestport.jpg
1152 ms
locationImages%2FsoupBowl.jpg
1148 ms
locationImages%2Fwaitpinga.jpg
1168 ms
locationImages%2Fcloud9.jpg
1134 ms
locationImages%2Fcloudbreak.jpg
1190 ms
locationImages%2FreveHavn.jpg
1065 ms
locationImages%2FlaSaladita.jpg
1229 ms
locationImages%2Fgalinhas.jpg
1056 ms
locationImages%2Fchicama.jpg
1069 ms
locationImages%2FplayaHermosa.jpg
1100 ms
locationImages%2FnewPier.jpg
1098 ms
locationImages%2FsantaCatalina.jpg
1075 ms
locationImages%2FmountIrvine.jpg
1083 ms
locationImages%2Fencuentro.jpg
1165 ms
locationImages%2Fhikkaduwa.jpg
1104 ms
locationImages%2FlasFlores.jpg
1113 ms
locationImages%2FstClair.jpg
1107 ms
locationImages%2FstentRoad.jpg
1075 ms
locationImages%2Fbluff.jpg
1124 ms
locationImages%2FnoosaHeads.jpg
1088 ms
locationImages%2FsnapperRocks.jpg
1048 ms
locationImages%2FbyronBay.jpg
1094 ms
locationImages%2Fjialeshuei.jpg
1116 ms
locationImages%2FcapeThreePoints.jpg
1141 ms
locationImages%2FtLand.jpg
1090 ms
locationImages%2FbarraBeach.jpg
1104 ms
locationImages%2Fwhangamata.jpg
1101 ms
locationImages%2Fflorianopolis.jpg
1062 ms
locationImages%2FkudakaJima.jpg
1170 ms
locationImages%2FlittleMalibu.jpg
1156 ms
locationImages%2Findicas.jpg
1070 ms
locationImages%2Fqueenscliff.jpg
1148 ms
locationImages%2FcocoaBeach.jpg
1102 ms
locationImages%2FcowBay.jpg
1083 ms
locationImages%2FbigWaveBay.jpg
1174 ms
locationImages%2Fjailbreaks.jpg
1178 ms
locationImages%2FfriscoPier.jpg
1153 ms
locationImages%2Fubatuba.jpg
1094 ms
locationImages%2FarugamBay.jpg
1110 ms
locationImages%2FlaPaloma.jpg
1103 ms
locationImages%2Fpopoyo.jpg
1299 ms
locationImages%2Fkamogawa.jpg
1124 ms
locationImages%2FtheWashout.jpg
1138 ms
locationImages%2Fyumuri.jpg
1162 ms
locationImages%2FbostonBay.jpg
1053 ms
locationImages%2FlongBeach.jpg
1058 ms
locationImages%2Fikumihama.jpg
1169 ms
locationImages%2FbagaBeach.jpg
1134 ms
locationImages%2Fgalveston.jpg
1139 ms
locationImages%2FcaboLedo.jpg
1045 ms
locationImages%2FfishermanPoint.jpg
1117 ms
locationImages%2FkaronBeach.jpg
1118 ms
locationImages%2FlawsonsBay.jpg
1154 ms
locationImages%2Fmarina.jpg
1093 ms
locationImages%2Fmotels.jpg
1044 ms
locationImages%2Fpiscinas.jpg
1086 ms
locationImages%2Fpoovar.jpg
1133 ms
locationImages%2Fpreveli.jpg
1139 ms
locationImages%2FpuraranBay.jpg
1075 ms
locationImages%2Fsalani.jpg
1031 ms
locationImages%2FskeletonBay.jpg
1078 ms
locationImages%2Fylig.jpg
1044 ms
johnjohn-florence.com accessibility score
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
Buttons do not have an accessible name
johnjohn-florence.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
johnjohn-florence.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnjohn-florence.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 Johnjohn-florence.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.
johnjohn-florence.com
Open Graph data is detected on the main page of Johnjohn Florence. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: