8.8 sec in total
194 ms
3.4 sec
5.3 sec
Click here to check amazing Patentlyapple content for United States. Otherwise, check out these important facts you probably never knew about patentlyapple.com
Patently Apple is an Apple Inc. centric blog focused on dissecting Apple's latest Intellectual Property. We mainly report on Apple's patent applications, granted patents and trademark filings that hav...
Visit patentlyapple.comWe analyzed Patentlyapple.com page load time and found that the first response time was 194 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
patentlyapple.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value9.8 s
0/100
25%
Value28.7 s
0/100
10%
Value7,490 ms
0/100
30%
Value0.024
100/100
15%
Value39.1 s
0/100
10%
194 ms
163 ms
12 ms
28 ms
8 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 76% of them (64 requests) were addressed to the original Patentlyapple.com, 10% (8 requests) were made to Static.typepad.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Patentlyapple.com.
Page size can be reduced by 1.0 MB (21%)
4.9 MB
3.9 MB
In fact, the total size of Patentlyapple.com main page is 4.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. 55% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 108.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 14.9 kB, which is 12% 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 108.2 kB or 88% of the original size.
Potential reduce by 815.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. Obviously, Patentlyapple needs image optimization as it can save up to 815.8 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
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 38% 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. Patentlyapple.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 12 (14%)
83
71
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Patentlyapple. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.patentlyapple.com
194 ms
styles.css
163 ms
thumbnail-gallery-min.js
12 ms
recommend.js
28 ms
quant.js
8 ms
print.css
86 ms
base-weblog.css
242 ms
bxslider.css
168 ms
widgets.css
163 ms
recentpostsfancy.css
167 ms
tipjar.css
162 ms
screen.css
164 ms
ga.js
191 ms
patently-apple-bg.jpg
165 ms
follow_us-c.png
170 ms
patently-apple-banner-4.png
145 ms
6a0120a5580826970c01b8d1a054e6970c-800wi
145 ms
6a0120a5580826970c01bb08bb018b970d-800wi
437 ms
6a0120a5580826970c01b8d1a04e8b970c-800wi
301 ms
6a0120a5580826970c01b7c81627d1970b-800wi
434 ms
6a0120a5580826970c01bb08badbfb970d-800wi
312 ms
6a0120a5580826970c01b8d1a02f9f970c-800wi
318 ms
6a0120a5580826970c01b8d19ff4aa970c-800wi
292 ms
6a0120a5580826970c01b8d1a002d2970c-800wi
541 ms
6a0120a5580826970c01bb08ba8e1e970d-800wi
301 ms
6a0120a5580826970c01bb08ba8e25970d-800wi
432 ms
6a0120a5580826970c01b8d19f9100970c-800wi
418 ms
6a0120a5580826970c01b7c8156950970b-800wi
434 ms
6a0120a5580826970c01b7c8151741970b-800wi
425 ms
6a0120a5580826970c01bb08b9e434970d-800wi
1077 ms
6a0120a5580826970c01bb08b9d0a3970d-800wi
426 ms
6a0120a5580826970c01b7c81502c9970b-800wi
431 ms
6a0120a5580826970c01b8d19f219e970c-800wi
531 ms
6a0120a5580826970c01bb08b9cac9970d-800wi
565 ms
6a0120a5580826970c01b8d19f1347970c-800wi
533 ms
6a0120a5580826970c01bb08b9bab9970d-800wi
920 ms
6a0120a5580826970c01b7c814ebb1970b-800wi
545 ms
6a0120a5580826970c01b8d19f10c6970c-800wi
1076 ms
6a0120a5580826970c01b7c814ce7e970b-800wi
564 ms
6a0120a5580826970c01b7c814ce82970b-800wi
704 ms
6a0120a5580826970c01b8d19ed45d970c-800wi
632 ms
6a0120a5580826970c01bb08b97ce1970d-800wi
1189 ms
6a0120a5580826970c01bb08b973e7970d-800wi
688 ms
6a0120a5580826970c01b8d19ecbb1970c-800wi
1386 ms
6a0120a5580826970c01b7c8149cd3970b-800wi
878 ms
6a0120a5580826970c01bb08b96971970d-800wi
1032 ms
6a0120a5580826970c01b7c81469f1970b-800wi
1032 ms
6a0120a5580826970c01bb08b930ff970d-800wi
1071 ms
6a0120a5580826970c01b8d19e8c64970c-800wi
1777 ms
6a0120a5580826970c01b8d19e8617970c-800wi
1070 ms
6a0120a5580826970c01b8d19e861c970c-800wi
1747 ms
6a0120a5580826970c01b7c814571c970b-800wi
1084 ms
__utm.gif
54 ms
6a0120a5580826970c01b8d19e7c40970c-800wi
932 ms
6a0120a5580826970c01bb08b8f304970d-800wi
1005 ms
6a0120a5580826970c01bb08b8f30c970d-800wi
1081 ms
6a0120a5580826970c01b7c8142189970b-800wi
1005 ms
6a0120a5580826970c01bb08b8e961970d-800wi
1076 ms
6a0120a5580826970c01b7c814179c970b-800wi
1437 ms
6a0120a5580826970c01b8d19e3b54970c-800wi
1047 ms
6a0120a5580826970c01b7c8141520970b-800wi
1042 ms
6a0120a5580826970c01bb08b8dd3b970d-800wi
1309 ms
6a0120a5580826970c01b7c813bd1e970b-800wi
1117 ms
6a0120a5580826970c01b8d19ddf21970c-800wi
1121 ms
6a0120a5580826970c01b7c813af90970b-800wi
1193 ms
6a0120a5580826970c01b7c813af95970b-800wi
1362 ms
6a0120a5580826970c01b7c813a98b970b-800wi
1176 ms
6a0120a5580826970c01b8d19dca6a970c-800wi
1259 ms
6a0120a5580826970c01bb08b86aa9970d-800wi
1281 ms
6a0120a5580826970c01b8d19dc512970c-800wi
1933 ms
6a0120a5580826970c01b7c8137181970b-800wi
1335 ms
6a0120a5580826970c01bb08b80f71970d-800wi
1321 ms
6a0120a5580826970c01b8d19d67f2970c-800wi
1327 ms
all.js
161 ms
6a0120a5580826970c01b8d19d3fc4970c-800wi
1273 ms
6a0120a5580826970c01b7c8131e6b970b-800wi
1797 ms
6a0120a5580826970c01bb08b7e4d7970d-800wi
1257 ms
stats
222 ms
pixel;r=2114236920;a=p-fcYWUmj5YbYKM;tags=typepad.extended;fpan=1;fpa=P0-1041020237-1455624025538;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1455624025537;tzo=-180;ref=;url=http%3A%2F%2Fwww.patentlyapple.com%2F;ogl=
162 ms
beacon.js
162 ms
6a0120a5580826970c01b7c8131bc1970b-800wi
1136 ms
254 ms
xd_arbiter.php
188 ms
xd_arbiter.php
317 ms
patentlyapple.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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
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.
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
patentlyapple.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
patentlyapple.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Patentlyapple.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 Patentlyapple.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.
patentlyapple.com
Open Graph description is not detected on the main page of Patentlyapple. 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: