5.2 sec in total
147 ms
3.4 sec
1.6 sec
Welcome to frank151.com homepage info - get ready to check Frank151 best content for United States right away, or after learning these important things about frank151.com
Visit frank151.comWe analyzed Frank151.com page load time and found that the first response time was 147 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
frank151.com performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value19.9 s
0/100
25%
Value13.3 s
2/100
10%
Value2,850 ms
3/100
30%
Value0.535
14/100
15%
Value21.5 s
1/100
10%
147 ms
204 ms
60 ms
87 ms
87 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 3% of them (5 requests) were addressed to the original Frank151.com, 28% (42 requests) were made to Cdn.frank151.com and 7% (10 requests) were made to Sumome-140a.kxcdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cdn.frank151.com.
Page size can be reduced by 1.6 MB (37%)
4.3 MB
2.7 MB
In fact, the total size of Frank151.com main page is 4.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. 85% 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.4 MB which makes up the majority of the site volume.
Potential reduce by 218.3 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 218.3 kB or 87% of the original size.
Potential reduce by 72.3 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. Frank151 images are well optimized though.
Potential reduce by 373.6 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 373.6 kB or 62% of the original size.
Potential reduce by 923.9 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. Frank151.com needs all CSS files to be minified and compressed as it can save up to 923.9 kB or 92% of the original size.
Number of requests can be reduced by 84 (61%)
137
53
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frank151. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
frank151.com
147 ms
wp-emoji-release.min.js
204 ms
wp-insta.css
60 ms
form-themes.min.css
87 ms
style.css
87 ms
css
59 ms
font-awesome.min.css
59 ms
modernizr.custom.min.js
58 ms
jquery.js
299 ms
jquery-migrate.min.js
153 ms
load.sumome.com
695 ms
build.min.js
148 ms
gpt.js
149 ms
js.cookie.min.js
155 ms
cb-ext.js
129 ms
cb-scripts.min.js
130 ms
wp-embed.min.js
163 ms
count.js
132 ms
slimbox2.js
132 ms
gtm.js
374 ms
config.js
719 ms
frank151-logo-mobile4.png
254 ms
Harold-hunter-1-360x240.jpg
255 ms
christian-hosoi_057-1-360x240.jpg
255 ms
EDDIES_GOLD-360x240.jpg
260 ms
CAPTION-260x170.jpg
260 ms
Screen-Shot-2017-06-16-at-12.06.29-PM-copy-260x170.jpg
260 ms
F42_Hiphop1-260x170.jpg
246 ms
CAPTION-360x240.jpg
330 ms
G-SHOCK-TITLE-360x240.jpg
1146 ms
G_SHOCK-PERSONOFINTEREST_SEAN-360x240.jpg
328 ms
frank151-logo-nav-white.png
329 ms
Ccgp2isW8AINK_O-600x300.jpg
329 ms
Jerome-Baker-III-378x300.jpg
329 ms
mscleo-378x300.jpg
684 ms
MIA_BINGO-blank-01-759x300.jpg
665 ms
Ebonics-759x600.jpg
664 ms
bgkos07-378x300.jpg
685 ms
F43_StreetPhotos14-378x300.jpg
665 ms
IMG_3434.jpg
895 ms
Futura_2000-b-378x300.jpeg
715 ms
slack-imgs.com_-378x300.jpeg
715 ms
primitiive_book_MOCKUP-1_large.jpg
716 ms
frank_doom2_cover_mock_nobarcode.jpg
715 ms
FEMMESCOVER.jpg
896 ms
Scene7-1000x600.jpg
891 ms
90155.800-1200x600.jpg
800 ms
Evelina_3.jpg
894 ms
frank151-logo-footer.png
890 ms
integrator.js
652 ms
pubads_impl_175.js
691 ms
cb-widget-social-media-light.png
1056 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
440 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
441 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
450 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
450 ms
fontawesome-webfont.woff
881 ms
icomoon.ttf
868 ms
count.js
384 ms
750 ms
analytics.js
295 ms
atrk.js
629 ms
tfa.js
280 ms
pixel
280 ms
obtp.js
522 ms
fbevents.js
609 ms
ajs.js
513 ms
bindevent.do
495 ms
bg.jpg
479 ms
pixel
233 ms
pixel
231 ms
count.js
639 ms
ads
278 ms
pubads_impl_rendering_175.js
297 ms
container.html
282 ms
collect
168 ms
apstag.js
224 ms
trinity.js
385 ms
jstag
233 ms
ADTECH;cmd=bid;cors=yes;v=2;alias=Frank151_H1_728x90;grp=242;screenheight=768;screenwidth=1024;screendensity=1;kvscreenheight=768;kvscreenwidth=1024;kvscreendensity=1;kvviewportwidth=1680;kvviewportheight=1050;misc=1516942037287
207 ms
ADTECH;cmd=bid;cors=yes;v=2;alias=Frank151_H1_300x250;grp=242;screenheight=768;screenwidth=1024;screendensity=1;kvscreenheight=768;kvscreenwidth=1024;kvscreendensity=1;kvviewportwidth=1680;kvviewportheight=1050;misc=1516942037288
207 ms
ADTECH;cmd=bid;cors=yes;v=2;alias=Frank151_H1_300x50;grp=242;screenheight=768;screenwidth=1024;screendensity=1;kvscreenheight=768;kvscreenwidth=1024;kvscreendensity=1;kvviewportwidth=1680;kvviewportheight=1050;misc=1516942037288
203 ms
ADTECH;cmd=bid;cors=yes;v=2;alias=Frank151_H1_320x50;grp=242;screenheight=768;screenwidth=1024;screendensity=1;kvscreenheight=768;kvscreenwidth=1024;kvscreendensity=1;kvviewportwidth=1680;kvviewportheight=1050;misc=1516942037289
206 ms
loader.js
170 ms
collect
296 ms
pixel
200 ms
pixel
100 ms
atrk.gif
265 ms
432800547119941
158 ms
pixel
190 ms
pixel
190 ms
pixel
189 ms
pixel
190 ms
p1.0-SNAPSHOT.143%2C395.do&a=true&e=click&ab=false
531 ms
impl.291-311-RELEASE.js
150 ms
beacon.js
250 ms
bid
421 ms
test.png
612 ms
services.js
165 ms
313 ms
ad
313 ms
generic
291 ms
acj
261 ms
generic
89 ms
us.gif
91 ms
info2
107 ms
us.gif
76 ms
sumome-image-sharer.css
63 ms
sumome-share-client.css
91 ms
us.gif
132 ms
us.gif
118 ms
css
116 ms
unknownbrowser.do
118 ms
14 ms
iu3
53 ms
load
249 ms
load
367 ms
us.gif
6 ms
pr
5 ms
getuid
9 ms
pd
23 ms
pixel
28 ms
pixel
46 ms
pixel
45 ms
pixel
45 ms
pixel
25 ms
pixel
44 ms
3f804197-d73f-a1a7-7ffc-28257438d964
59 ms
cfcm.ashx
89 ms
openx
26 ms
p
42 ms
sd
33 ms
sd
32 ms
sd
21 ms
464246.gif
19 ms
sd
17 ms
sd
5 ms
closelabel.gif
128 ms
facebook-white-60.png
79 ms
pinterest-white-60.png
46 ms
twitter-white-60.png
59 ms
googleplus-white-60.png
60 ms
stumbleupon-white-60.png
58 ms
email-white-60.png
59 ms
sumome-white-60.png
59 ms
sd
82 ms
ads
174 ms
gpt.js
27 ms
sd
15 ms
frank151.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
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.
frank151.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
Missing source maps for large first-party JavaScript
frank151.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
Image elements do not have [alt] attributes
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 Frank151.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 Frank151.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.
frank151.com
Open Graph description is not detected on the main page of Frank151. 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: