3.2 sec in total
763 ms
2.2 sec
260 ms
Click here to check amazing Old Phone Shop content. Otherwise, check out these important facts you probably never knew about oldphoneshop.com
Old Phone Shop, Vintage, Telephones, Rotary Phones, Antique Telephones, Telephone Parts, Candlestick Telephones, Antique Telephone Repair
Visit oldphoneshop.comWe analyzed Oldphoneshop.com page load time and found that the first response time was 763 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
oldphoneshop.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value3.5 s
63/100
25%
Value4.4 s
74/100
10%
Value320 ms
77/100
30%
Value0.829
4/100
15%
Value9.0 s
34/100
10%
763 ms
26 ms
48 ms
70 ms
92 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Oldphoneshop.com, 32% (29 requests) were made to Cdn5.bigcommerce.com and 21% (19 requests) were made to Cdn6.bigcommerce.com. The less responsive or slowest element that took the longest time to load (763 ms) belongs to the original domain Oldphoneshop.com.
Page size can be reduced by 668.7 kB (23%)
2.9 MB
2.2 MB
In fact, the total size of Oldphoneshop.com main page is 2.9 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 72.4 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 72.4 kB or 79% of the original size.
Potential reduce by 11.8 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. Old Phone Shop images are well optimized though.
Potential reduce by 455.1 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 455.1 kB or 70% of the original size.
Potential reduce by 129.4 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. Oldphoneshop.com needs all CSS files to be minified and compressed as it can save up to 129.4 kB or 81% of the original size.
Number of requests can be reduced by 49 (60%)
82
33
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Old Phone Shop. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
oldphoneshop.com
763 ms
css
26 ms
font-awesome.css
48 ms
styles.css
70 ms
font-awesome.css
92 ms
iselector.css
90 ms
flexslider.css
91 ms
slide-show.css
90 ms
styles-slide-show.css
90 ms
social.css
89 ms
styles.css
24 ms
light.css
109 ms
theme.css
110 ms
grid.css
109 ms
artify.css
107 ms
responsive.css
107 ms
custom.css
33 ms
product.attributes.css
90 ms
ui.all.css
91 ms
product.quickview.css
114 ms
imodal.css
121 ms
jquery.min.js
36 ms
menudrop.js
31 ms
iselector.js
31 ms
css
32 ms
css
32 ms
matchMedia.js
40 ms
common.js
43 ms
imagesLoaded.js
43 ms
jquery.autobox.js
41 ms
init.js
39 ms
jquery.uniform.min.js
59 ms
quicksearch.js
57 ms
jquery.cycle2.min.js
57 ms
main.js
59 ms
faceted-search.css
54 ms
responsive-partner.css
39 ms
jquery-ui.min.js
108 ms
jquery.validate.js
107 ms
product.functions.js
108 ms
product.attributes.js
106 ms
quickview.js
109 ms
quickview.initialise.js
108 ms
jquery.form.js
158 ms
imodal.js
157 ms
visitor.js
107 ms
ga.js
217 ms
beacon_api.js
197 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
196 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
196 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
197 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
196 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
196 ms
analytics.min.js
194 ms
sdk.js
193 ms
loader.png
193 ms
thumbnail_old-phone-shop-logo_1_1462393953__34316.jpg
192 ms
index.php
438 ms
IcoRating0.png
79 ms
ProductDefault.gif
80 ms
IcoRating5.png
78 ms
menu-arrow.png
78 ms
Phone_banner_1250x375_edited-1.png
78 ms
Parts_banner_1250x375_edited-1.png
79 ms
upsi4__60459.1504216310.200.200.JPG
79 ms
sin__40235.1504216313.200.200.JPG
78 ms
ef__69651.1503583495.200.200.JPG
78 ms
DSC05348__31288.1489612132.200.200.JPG
78 ms
DSC03325__82230.1457578925.200.200.JPG
82 ms
crad__65949.1414365644.200.200.JPG
81 ms
payphonehistory_book__76849.1437058184.200.200.jpg
82 ms
handset_cord_nice__12202.1325218201.200.200.JPG
82 ms
mouth__97173.1316747453.200.200.JPG
80 ms
candlestick_cord__83414.1326578034.200.200.JPG
80 ms
e1__81677.1316273361.200.200.JPG
127 ms
dialgizmo_2001__55054.1365157417.200.200.jpg
127 ms
visa-mc-disc.png
79 ms
fontawesome-webfont.woff
77 ms
fontawesome-webfont.woff
78 ms
__utm.gif
66 ms
merchant.js
325 ms
fornax.min.js
35 ms
106 ms
0sTQzbapM8j.js
21 ms
0sTQzbapM8j.js
26 ms
upstream
261 ms
upstream
227 ms
upstream
230 ms
77fd3b70e09001329fd57a163e74bed5.gif
110 ms
9137fa40e09101329fdc7a163e74bed5.gif
15 ms
oldphoneshop.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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
oldphoneshop.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
oldphoneshop.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Oldphoneshop.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 Oldphoneshop.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.
oldphoneshop.com
Open Graph description is not detected on the main page of Old Phone Shop. 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: