3.1 sec in total
401 ms
2.5 sec
180 ms
Visit ozlines.com now to see the best up-to-date Ozlines content and also check out these interesting facts you probably never knew about ozlines.com
surfshop, surf shop, surfboard kopen, surfboard sock, surfboard fins, surfboard kopen beginners, surfles, surfschool, ozlines, surfkampen, surf camps, wetsuits, surfboards, surf coaching, surfing, huu...
Visit ozlines.comWe analyzed Ozlines.com page load time and found that the first response time was 401 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
ozlines.com performance score
401 ms
1093 ms
178 ms
175 ms
181 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 33% of them (22 requests) were addressed to the original Ozlines.com, 30% (20 requests) were made to Static.xx.fbcdn.net and 14% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ozlines.com.
Page size can be reduced by 111.3 kB (17%)
642.7 kB
531.4 kB
In fact, the total size of Ozlines.com main page is 642.7 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. 65% of websites need less resources to load. Images take 482.2 kB which makes up the majority of the site volume.
Potential reduce by 13.0 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 1.9 kB, which is 11% 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 13.0 kB or 74% of the original size.
Potential reduce by 24.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. Ozlines images are well optimized though.
Potential reduce by 17.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 17.7 kB or 23% of the original size.
Potential reduce by 56.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. Ozlines.com needs all CSS files to be minified and compressed as it can save up to 56.0 kB or 85% of the original size.
Number of requests can be reduced by 32 (50%)
64
32
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ozlines. 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 12 to 1 for CSS and as a result speed up the page load time.
ozlines.com
401 ms
www.ozlines.com
1093 ms
base.css
178 ms
skeleton.css
175 ms
layout.css
181 ms
jquery.lightbox-0.5.css
183 ms
modernizr-2.5.3.min.js
289 ms
simplecart.css
191 ms
jquery.min.js
5 ms
jquery.lightbox-0.5.min.js
262 ms
script.js
273 ms
bg.jpg
557 ms
OzlinesSurf_logo_RGB.png
343 ms
winkelwagen.png
102 ms
strepen.jpg
333 ms
surfschool_new.jpg
338 ms
groepsuitjes_new.jpg
343 ms
fcs-tool_grande.17ec60e7830d869fdb36f8c6b9e5e3041.jpg
187 ms
Spudnick.bf7c2161f73840c585452482a2fd525a1.png
558 ms
EarPuttyEarPlugs-BOX_no-USAswim.17ec60e7830d869fdb36f8c6b9e5e3041.jpg
555 ms
dingallpolyesterrepairkit.17ec60e7830d869fdb36f8c6b9e5e3041.jpg
556 ms
widgets.js
89 ms
footerbg.jpg
544 ms
ga.js
9 ms
kids_surf_3.jpg
692 ms
__utm.gif
15 ms
likebox.php
324 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
122 ms
syndication
82 ms
372613682171084800
316 ms
kyEKgjk51ZE.css
42 ms
kTub4bakEmM.css
37 ms
kE_Z8j4XNUS.css
46 ms
q68gy-v_YMF.js
47 ms
FJmpeSpHpjS.js
43 ms
0wM5s1Khldu.js
40 ms
1bNoFZUdlYZ.js
43 ms
OloiM1PZafe.js
72 ms
LTv6ZK-5zxz.js
77 ms
1FCa-btixu2.js
92 ms
Oagsvfb4VWi.js
73 ms
pObvZSrFc_4.js
75 ms
Nn19HjwCsOL.js
75 ms
H3EKDTObx05.js
74 ms
OZFAYTv-ZUg.js
105 ms
12806103_1158258650880794_6906768052815981408_n.jpg
132 ms
551512_566268520079813_1791752315_n.jpg
36 ms
1426629_10151998882186605_1370687052_n.jpg
52 ms
12417844_10207585667536440_5973568921827718982_n.jpg
37 ms
12651265_10205689783512286_6916386354419628319_n.jpg
38 ms
1502548_996289887111642_4323538490490412929_n.jpg
174 ms
12804823_10153974612213684_331330777789953356_n.jpg
49 ms
12803220_986904891387128_7123266164096438345_n.jpg
92 ms
527113_10151515836254871_1366579689_n.jpg
115 ms
wL6VQj7Ab77.png
31 ms
s7jcwEQH7Sx.png
29 ms
gxbPuQdXIZP.png
30 ms
proxy.jpg
159 ms
1f4f7.png
92 ms
proxy.jpg
143 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
34 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
66 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
54 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
84 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
4 ms
ozlines.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozlines.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 Ozlines.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.
ozlines.com
Open Graph description is not detected on the main page of Ozlines. 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: