5.3 sec in total
272 ms
4.8 sec
210 ms
Visit phonoland.com now to see the best up-to-date Phonoland content for United States and also check out these interesting facts you probably never knew about phonoland.com
Talking machines and antiques collectors community since 1997. Forum subjects include jukeboxes, gramophones, phonographs, radios, 78rpm records, 45rpm vinyl and cylinder records.
Visit phonoland.comWe analyzed Phonoland.com page load time and found that the first response time was 272 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
phonoland.com performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
272 ms
505 ms
113 ms
925 ms
169 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 49% of them (45 requests) were addressed to the original Phonoland.com, 14% (13 requests) were made to Fonts.gstatic.com and 9% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Phonoland.com.
Page size can be reduced by 625.7 kB (63%)
1.0 MB
374.6 kB
In fact, the total size of Phonoland.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. 70% of websites need less resources to load. Javascripts take 476.0 kB which makes up the majority of the site volume.
Potential reduce by 43.9 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 9.8 kB, which is 19% 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 43.9 kB or 83% of the original size.
Potential reduce by 10.0 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. Phonoland images are well optimized though.
Potential reduce by 304.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 304.0 kB or 64% of the original size.
Potential reduce by 267.8 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. Phonoland.com needs all CSS files to be minified and compressed as it can save up to 267.8 kB or 84% of the original size.
Number of requests can be reduced by 45 (61%)
74
29
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phonoland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
phonoland.com
272 ms
www.phonoland.com
505 ms
font-awesome.min.css
113 ms
jquery.min.js
925 ms
grey.css
169 ms
icheck.min.js
2818 ms
stylesheet.css
1814 ms
mobbern.css
200 ms
mobbern-responsive.css
253 ms
color-theme-slate.css
285 ms
color-theme.css
336 ms
style.css
368 ms
imageset.css
419 ms
cookieconsent.latest.min.js
31 ms
platform.js
61 ms
adsbygoogle.js
26 ms
core.js
452 ms
bootstrap.min.js
503 ms
jquery.nicescroll.js
631 ms
jquery.cookie.js
586 ms
mobbern-js.js
671 ms
forum_fn.js
718 ms
ajax.js
755 ms
common.css
87 ms
links.css
88 ms
content.css
89 ms
buttons.css
88 ms
cp.css
90 ms
forms.css
90 ms
colours.css
173 ms
imageset.css
170 ms
bootstrap.css
256 ms
css
25 ms
css
37 ms
analytics.js
24 ms
phonoland_2015.png
392 ms
forum_icon_lounge.jpg
120 ms
forum_icon_pride_joy.jpg
121 ms
forum_icon_for_sale.jpg
119 ms
forum_icon_wanted.jpg
120 ms
forum_icon_antique_radios.jpg
120 ms
forum_icon_jukebox.jpg
238 ms
forum_icon_gramophones_phonographs.jpg
238 ms
forum_icon_electronic_gramophones_phonographs.jpg
239 ms
forum_icon_78_rpm_records_and_cylinders.jpg
237 ms
forum_icon_45_33_rpm_records.jpg
237 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
55 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
56 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
56 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
55 ms
ca-pub-2787753393086508.js
188 ms
zrt_lookup.html
184 ms
show_ads_impl.js
104 ms
collect
136 ms
fontawesome-webfont.woff
472 ms
dazS1PrQQuCxC3iOAJFEJR_xHqYgAV9Bl_ZQbYUxnQU.woff
131 ms
MEz38VLIFL-t46JUtkIEgCeJLMOzE6CCkidNEpZOseY.woff
130 ms
y7lebkjgREBJK96VQi37ZobN6UDyHWBl620a-IRfuBk.woff
42 ms
dazS1PrQQuCxC3iOAJFEJTqR_3kx9_hJXbbyU8S6IN0.woff
130 ms
forum_read.svg
273 ms
ads
187 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
33 ms
PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff
33 ms
PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff
159 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
32 ms
osd.js
135 ms
loading.gif
152 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
75 ms
fastbutton
106 ms
grey.png
131 ms
ads
244 ms
ads
226 ms
postmessageRelay
58 ms
cb=gapi.loaded_0
24 ms
cb=gapi.loaded_1
23 ms
3193398744-postmessagerelay.js
70 ms
rpc:shindig_random.js
29 ms
print.css
100 ms
cb=gapi.loaded_0
4 ms
css
81 ms
m_js_controller.js
45 ms
abg.js
44 ms
27722-218796-36959-638
65 ms
300x600_AQ-1_PSBSUPR.jpg
201 ms
nessie_icon_tiamat_white.png
21 ms
s
15 ms
googlelogo_color_112x36dp.png
23 ms
x_button_blue2.png
4 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
13 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
59 ms
phonoland.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
Document doesn't have a <title> element
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
phonoland.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
phonoland.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phonoland.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 Phonoland.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.
phonoland.com
Open Graph data is detected on the main page of Phonoland. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: