5.3 sec in total
297 ms
3.4 sec
1.5 sec
Visit mobifile.co now to see the best up-to-date Mobifile content for United States and also check out these interesting facts you probably never knew about mobifile.co
Visit mobifile.coWe analyzed Mobifile.co page load time and found that the first response time was 297 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.
mobifile.co performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value3.0 s
77/100
25%
Value2.5 s
98/100
10%
Value100 ms
98/100
30%
Value0.014
100/100
15%
Value3.2 s
94/100
10%
297 ms
298 ms
24 ms
437 ms
41 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 74% of them (23 requests) were addressed to the original Mobifile.co, 10% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Mobifile.co.
Page size can be reduced by 862.9 kB (29%)
3.0 MB
2.2 MB
In fact, the total size of Mobifile.co main page is 3.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. 30% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 7.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 1.4 kB, which is 13% 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 7.9 kB or 70% of the original size.
Potential reduce by 775.4 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. Obviously, Mobifile needs image optimization as it can save up to 775.4 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 45.3 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 45.3 kB or 61% of the original size.
Potential reduce by 34.3 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. Mobifile.co needs all CSS files to be minified and compressed as it can save up to 34.3 kB or 86% of the original size.
Number of requests can be reduced by 3 (12%)
26
23
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobifile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
main.html
297 ms
main.css
298 ms
css
24 ms
animations.css
437 ms
jquery.min.js
41 ms
popup.css
301 ms
popup.js
426 ms
analytics.js
71 ms
en_generic_rgb_wo_60.png
140 ms
mobifileLogoWhite.png
291 ms
patternFooter.png
1597 ms
NexusHead.png
2118 ms
nexusFull2.png
1229 ms
dropboxIcon.png
434 ms
gmailIcon.png
435 ms
driveIcon.png
844 ms
swipe2.png
1609 ms
lock.png
715 ms
tagIcon.png
980 ms
commentsIcon.png
1133 ms
shareIcon.png
1254 ms
Nexus.png
1679 ms
devices.png
1904 ms
facebook.png
1526 ms
google+.png
1793 ms
linkedin.png
1864 ms
twitter.png
1890 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
24 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
37 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
38 ms
collect
28 ms
mobifile.co 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.
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
<frame> or <iframe> elements do not have a title
mobifile.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
mobifile.co 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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobifile.co can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Mobifile.co 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.
mobifile.co
Open Graph description is not detected on the main page of Mobifile. 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: