3.5 sec in total
205 ms
3 sec
385 ms
Click here to check amazing Myown Fone content. Otherwise, check out these important facts you probably never knew about myownfone.com
OwnFone and Footprint GPS Trackers. Easy to use telecare technology for the young, elderly and vulnerable.
Visit myownfone.comWe analyzed Myownfone.com page load time and found that the first response time was 205 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
myownfone.com performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value13.8 s
0/100
25%
Value9.1 s
14/100
10%
Value2,090 ms
7/100
30%
Value0.341
33/100
15%
Value13.2 s
12/100
10%
205 ms
322 ms
740 ms
314 ms
266 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Myownfone.com, 61% (40 requests) were made to Ownfone.com and 17% (11 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Ownfone.com.
Page size can be reduced by 730.6 kB (22%)
3.3 MB
2.6 MB
In fact, the total size of Myownfone.com main page is 3.3 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. 45% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 251.7 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 251.7 kB or 80% of the original size.
Potential reduce by 158.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. Myown Fone images are well optimized though.
Potential reduce by 217.8 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 217.8 kB or 71% of the original size.
Potential reduce by 102.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. Myownfone.com needs all CSS files to be minified and compressed as it can save up to 102.4 kB or 81% of the original size.
Number of requests can be reduced by 20 (38%)
52
32
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Myown Fone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
myownfone.com
205 ms
myownfone.com
322 ms
www.ownfone.com
740 ms
text_style.css
314 ms
def5oxv.js
266 ms
prefixfree.min.js
159 ms
jquery.min.js
48 ms
embed.js
160 ms
modernizr.js
161 ms
cookie-notice.js
164 ms
50306.js
105 ms
pinit.js
45 ms
functions.js
445 ms
www.ownfone.com
29 ms
analytics.js
112 ms
pinit_fg_en_round_red_32.png
87 ms
flag-uk.png
125 ms
design-modal-img-01.png
174 ms
design-modal-img-02.png
174 ms
design-modal-img-03.png
174 ms
icon-globe.png
124 ms
logo-kickstarter.png
125 ms
phone-img-front.png
373 ms
phone-img-back.png
448 ms
logo.png
353 ms
share.png
365 ms
close.png
371 ms
search.png
364 ms
fones-02.svg
365 ms
slide1-jpg
911 ms
slide2-jpg
1055 ms
slide3-jpg
1053 ms
footprint-hero1-jpg
1252 ms
fone-lanyard.png
570 ms
fones-01.svg
540 ms
fones-03.svg
617 ms
fones-04.svg
638 ms
step-1.png
682 ms
step-2.png
798 ms
step-3.png
764 ms
logo-age-uk.png
844 ms
logo-stroke.png
883 ms
logo-diabetes.png
924 ms
logo-mencap.png
967 ms
logo-nkf.png
988 ms
logo-strokes.png
1005 ms
text_style.css
1116 ms
www.ownfone.com
58 ms
pinit_main.js
34 ms
collect
43 ms
xK0wVLUC9YcpYVtk0IWu3RjJik6whpPSlB8kKKBeNbGffVRKMUM-eMJ6Mk6f5Mb.woff
241 ms
c_feXCItrcmnUuFqPkfGM3X9R57CastfARb4rkZM4KCffVnKMUM-eMJ6Mk6f5M9.woff
416 ms
0bElPkVQTcHMRq20cNlgwcTVcuR3rERMNLE2pd3cC3MffVdKMUM-eMJ6Mk6f5Mw.woff
480 ms
AG3779V02mlvqwPYGRxSqxmqlNArHz55tFRXOULlh_MffVDKMUM-eMJ6Mk6f5MS.woff
416 ms
ownfone.woff
949 ms
xDWiu-dI2QEtHSTzsJMJbII7eOs0P_5LgUgHPDdWj4wffV1KMUM-eMJ6Mk6f5Mt.woff
415 ms
2WI8u72cPnJ9L4XcSpVRVsc0wwVLJs-ueKPAHHysFCbffVzKMUM-eMJ6Mk6f5Mv.woff
385 ms
2bQg_-2yY6wPoxdijP5mtjsUxTIuDClu2gYPJUOUILtffVLKMUM-eMJ6Mk6f5MX.woff
413 ms
HCe9s9QUDhDgO9AXA082chxDoX6Ll3oXEekJREFflS3ffVaKMUM-eMJ6Mk6f5gI.woff
560 ms
collect
239 ms
cookieconsent.silktide.com
235 ms
0754.js
42 ms
ga-audiences
94 ms
p.gif
177 ms
closeIcon2.png
491 ms
iframe_api
35 ms
myownfone.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
myownfone.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
Page has valid source maps
myownfone.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myownfone.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 Myownfone.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.
myownfone.com
Open Graph description is not detected on the main page of Myown Fone. 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: