2.3 sec in total
310 ms
1.8 sec
152 ms
Welcome to oldloft.com homepage info - get ready to check Oldloft best content right away, or after learning these important things about oldloft.com
The domain name oldloft.com is for sale. Make an offer or buy it now at a set price.
Visit oldloft.comWe analyzed Oldloft.com page load time and found that the first response time was 310 ms and then it took 2 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.
oldloft.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.4 s
67/100
25%
Value3.8 s
83/100
10%
Value450 ms
62/100
30%
Value0.039
99/100
15%
Value8.0 s
42/100
10%
310 ms
99 ms
191 ms
292 ms
195 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 18% of them (19 requests) were addressed to the original Oldloft.com, 20% (22 requests) were made to Static.xx.fbcdn.net and 19% (21 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (518 ms) relates to the external source Facebook.com.
Page size can be reduced by 246.0 kB (24%)
1.0 MB
760.3 kB
In fact, the total size of Oldloft.com main page is 1.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. 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 670.5 kB which makes up the majority of the site volume.
Potential reduce by 7.5 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 7.5 kB or 64% of the original size.
Potential reduce by 30.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. Oldloft images are well optimized though.
Potential reduce by 120.9 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 120.9 kB or 55% of the original size.
Potential reduce by 87.5 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. Oldloft.com needs all CSS files to be minified and compressed as it can save up to 87.5 kB or 82% of the original size.
Number of requests can be reduced by 55 (53%)
103
48
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oldloft. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
oldloft.com
310 ms
style.css
99 ms
jetpack.css
191 ms
jquery.js
292 ms
jquery-migrate.min.js
195 ms
external-tracking.min.js
194 ms
show_ads.js
5 ms
devicepx-jetpack.js
4 ms
gprofiles.js
56 ms
wpgroho.js
235 ms
e-201611.js
5 ms
extras.css
100 ms
wp-emoji-release.min.js
118 ms
analytics.js
34 ms
kubrickbgcolor.jpg
167 ms
pointer-green.png
157 ms
rounded-corners.svg
157 ms
oldloft.png
152 ms
content.png
163 ms
team.png
395 ms
footer.png
205 ms
pointer-grey.png
205 ms
ca-pub-2766881216380851.js
148 ms
zrt_lookup.html
134 ms
show_ads_impl.js
67 ms
NuevaStd-Regular.otf
352 ms
widgets.js
136 ms
collect
92 ms
wordpress.png
143 ms
hovercard.css
80 ms
services.css
82 ms
g.gif
72 ms
ads
304 ms
osd.js
50 ms
likebox.php
518 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
137 ms
syndication
86 ms
366499509284503552
247 ms
m_js_controller.js
17 ms
abg.js
34 ms
favicon
51 ms
googlelogo_color_112x36dp.png
38 ms
nessie_icon_tiamat_white.png
34 ms
s
19 ms
x_button_blue2.png
8 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
proxy.jpg
74 ms
proxy.jpg
175 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
30 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
73 ms
pFuf0ag6_normal.png
54 ms
M63SopQJ_normal.jpg
50 ms
ce76CDMD_normal.jpg
59 ms
T4BHYbAE_normal.jpg
122 ms
uhGmfNwj_normal.png
58 ms
fFFdS8fU_normal.png
120 ms
ediRdEXK_normal.png
58 ms
CBarWGHj_normal.jpg
57 ms
jDHch5Fh_normal.png
62 ms
nhhiAmjP_normal.jpg
62 ms
Obj7VasE_normal.jpeg
62 ms
CcuNZ5pXEAAgPr5.jpg:small
117 ms
CctBj0ZW4AAeo7Q.jpg:small
126 ms
CcnWp4fW0AEI-sR.jpg:small
331 ms
CcEKnioWAAEV7C5.jpg:small
125 ms
CcZxk7KUMAI2-VI.jpg:small
359 ms
CcZxk6LUEAArZMC.jpg:small
322 ms
CcJ4n9FVIAAfjx1.jpg:small
320 ms
CcJ4oUEVAAAZnIn.jpg:small
331 ms
CcJ4oM1UUAAe3xi.jpg:small
332 ms
CcJ4oOPUcAAC6Jb.jpg:small
329 ms
kyEKgjk51ZE.css
93 ms
kTub4bakEmM.css
109 ms
Czh0gDTFcBt.css
117 ms
N-k91nHCZS2.css
119 ms
ZeuPykSxSED.css
124 ms
q68gy-v_YMF.js
117 ms
FJmpeSpHpjS.js
158 ms
0wM5s1Khldu.js
157 ms
1bNoFZUdlYZ.js
156 ms
njO1TPvGzoR.js
173 ms
1QuX41zDRrx.js
171 ms
Oagsvfb4VWi.js
170 ms
LTv6ZK-5zxz.js
179 ms
1FCa-btixu2.js
178 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
44 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
80 ms
proxy.jpg
169 ms
11214078_10153463194043192_7161042184283014638_n.png
210 ms
safe_image.php
171 ms
safe_image.php
113 ms
safe_image.php
72 ms
12047200_10153377540323192_4100298751798960235_n.png
54 ms
12794551_10153675678713192_4408645735735812644_n.jpg
171 ms
12809627_10153675679128192_8354035945936857936_n.jpg
168 ms
12799067_10153675678733192_8098747780411008143_n.jpg
169 ms
12801694_10153675678763192_6626039963940057881_n.jpg
134 ms
wL6VQj7Ab77.png
52 ms
s7jcwEQH7Sx.png
51 ms
sSwLTfB7PfP.png
51 ms
pimRBh7B6ER.png
51 ms
QDwYpIaRyfG.png
51 ms
_Gr8Yagnmzs.png
51 ms
proxy.jpg
95 ms
I6-MnjEovm5.js
8 ms
pQrUxxo5oQp.js
7 ms
collect
11 ms
ui
31 ms
oldloft.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
oldloft.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
Browser errors were logged to the console
Page has valid source maps
oldloft.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oldloft.com 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 Oldloft.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.
oldloft.com
Open Graph data is detected on the main page of Oldloft. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: