6.6 sec in total
607 ms
3.8 sec
2.2 sec
Visit patentlymobile.com now to see the best up-to-date Patently Mobile content for United States and also check out these interesting facts you probably never knew about patentlymobile.com
Patently Mobile is a specialized Intellectual Property centric blog that energetically and enthusiastically reports on the hottest patents from the likes of Google, Microsoft, Samsung and others. Our ...
Visit patentlymobile.comWe analyzed Patentlymobile.com page load time and found that the first response time was 607 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
patentlymobile.com performance score
607 ms
143 ms
94 ms
124 ms
85 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Patentlymobile.com, 68% (43 requests) were made to Patentbolt.typepad.com and 13% (8 requests) were made to Static.typepad.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Patentbolt.typepad.com.
Page size can be reduced by 301.6 kB (15%)
2.0 MB
1.7 MB
In fact, the total size of Patentlymobile.com main page is 2.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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 69.2 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 10.6 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 69.2 kB or 88% of the original size.
Potential reduce by 155.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. Patently Mobile images are well optimized though.
Potential reduce by 26.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 26.0 kB or 36% of the original size.
Potential reduce by 51.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. Patentlymobile.com needs all CSS files to be minified and compressed as it can save up to 51.4 kB or 82% of the original size.
Number of requests can be reduced by 13 (21%)
62
49
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Patently Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.patentlymobile.com
607 ms
styles.css
143 ms
thumbnail-gallery-min.js
94 ms
recommend.js
124 ms
quant.js
85 ms
print.css
109 ms
base-weblog.css
469 ms
bxslider.css
168 ms
widgets.css
254 ms
recentpostsfancy.css
257 ms
tipjar.css
258 ms
screen.css
276 ms
analytics.js
120 ms
patently-mobile-bg.png
281 ms
patently-mobile-banner.png
307 ms
6a0168e68320b0970c01bb08ca9cc3970d-800wi
229 ms
6a0168e68320b0970c01b8d1b08701970c-800wi
353 ms
6a0168e68320b0970c01b8d1ae75d1970c-800wi
208 ms
6a0168e68320b0970c01b7c8243ce9970b-800wi
545 ms
6a0168e68320b0970c01bb08c81b7b970d-800wi
371 ms
6a0168e68320b0970c01b7c8239156970b-800wi
664 ms
6a0168e68320b0970c01b8d1a96b6d970c-800wi
540 ms
6a0168e68320b0970c01b8d1a96b97970c-800wi
781 ms
6a0168e68320b0970c01bb08c33121970d-800wi
732 ms
6a0168e68320b0970c01b8d1a8834f970c-800wi
856 ms
6a0168e68320b0970c01b7c81cdcfb970b-800wi
712 ms
6a0168e68320b0970c01b8d1a6f593970c-800wi
873 ms
6a0168e68320b0970c01bb08c0a95f970d-800wi
822 ms
6a0168e68320b0970c01bb08c0a96d970d-800wi
1183 ms
6a0168e68320b0970c01bb08bd2a66970d-800wi
927 ms
6a0168e68320b0970c01b8d1a283cc970c-800wi
1050 ms
6a0168e68320b0970c01bb08bad9a1970d-800wi
982 ms
6a0168e68320b0970c01b7c8160709970b-800wi
1119 ms
6a0168e68320b0970c01bb08ba31f9970d-800wi
1038 ms
6a0168e68320b0970c01b7c815628a970b-800wi
1314 ms
6a0168e68320b0970c01b8d19d60c6970c-800wi
1153 ms
6a0168e68320b0970c01b7c8133e76970b-800wi
1229 ms
6a0168e68320b0970c01b8d19cdda1970c-800wi
1168 ms
6a0168e68320b0970c01b7c812bbe2970b-800wi
1322 ms
6a0168e68320b0970c01b8d19c6c26970c-800wi
1317 ms
6a0168e68320b0970c01bb08b712e7970d-800wi
1348 ms
6a0168e68320b0970c01b8d19bece2970c-800wi
1361 ms
6a0168e68320b0970c01b7c80c0174970b-800wi
1418 ms
6a0168e68320b0970c01bb08b0d0c4970d-800wi
1921 ms
6a0168e68320b0970c01b7c809e372970b-800wi
1489 ms
6a0168e68320b0970c01b7c809e388970b-800wi
1531 ms
6a0168e68320b0970c01bb08ada826970d-800wi
1517 ms
6a0168e68320b0970c01b8d192ed9e970c-800wi
1537 ms
6a0168e68320b0970c01b7c8089e8f970b-800wi
1614 ms
collect
67 ms
6a0168e68320b0970c01bb08ad438a970d-800wi
1915 ms
6a0168e68320b0970c01b7c80369dc970b-800wi
1596 ms
6a0168e68320b0970c01b8d18d5677970c-800wi
1579 ms
6a0168e68320b0970c01b8d18d0b9f970c-800wi
1523 ms
6a0168e68320b0970c01bb08a7d0cd970d-800wi
1839 ms
6a0168e68320b0970c01bb08a54725970d-800wi
1768 ms
widgets.js
1216 ms
6a0168e68320b0970c01b8d18a8ecd970c-800wi
1635 ms
stats
303 ms
pixel;r=1723117369;a=p-fcYWUmj5YbYKM;tags=typepad.extended;fpan=1;fpa=P0-1761428457-1459153954152;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1459153954149;tzo=-180;ref=;url=http%3A%2F%2Fwww.patentlymobile.com%2F;ogl=
111 ms
beacon.js
114 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
341 ms
follow_button.64a917b4a230f163048902c783e1530f.en.html
69 ms
patentlymobile.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Patentlymobile.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 Patentlymobile.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.
patentlymobile.com
Open Graph description is not detected on the main page of Patently Mobile. 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: