6.6 sec in total
286 ms
4.5 sec
1.8 sec
Visit quitefranklyproductions.com now to see the best up-to-date Quite Frankly Productions content and also check out these interesting facts you probably never knew about quitefranklyproductions.com
Welcome to Quite Frankly Productions. Our videos have been connecting audiences since 2007 and in that time we’ve covered the world with hundreds of different stories. With offices in London, New York...
Visit quitefranklyproductions.comWe analyzed Quitefranklyproductions.com page load time and found that the first response time was 286 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
quitefranklyproductions.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value3.8 s
55/100
25%
Value10.4 s
8/100
10%
Value1,250 ms
19/100
30%
Value0.003
100/100
15%
Value18.5 s
3/100
10%
286 ms
465 ms
344 ms
470 ms
53 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 66% of them (56 requests) were addressed to the original Quitefranklyproductions.com, 26% (22 requests) were made to Unicons.iconscout.com and 2% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Quitefranklyproductions.com.
Page size can be reduced by 927.8 kB (14%)
6.5 MB
5.5 MB
In fact, the total size of Quitefranklyproductions.com main page is 6.5 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. 65% of websites need less resources to load. Images take 6.2 MB which makes up the majority of the site volume.
Potential reduce by 116.5 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 116.5 kB or 75% of the original size.
Potential reduce by 811.2 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, Quite Frankly Productions needs image optimization as it can save up to 811.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 22 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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. Quitefranklyproductions.com has all CSS files already compressed.
Number of requests can be reduced by 11 (20%)
56
45
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Quite Frankly Productions. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
quitefranklyproductions.com
286 ms
www.quitefranklyproductions.com
465 ms
style.min.css
344 ms
style.css
470 ms
css
53 ms
jquery.min.js
465 ms
jquery-migrate.min.js
443 ms
js
85 ms
line.css
78 ms
select2.min.css
50 ms
js
93 ms
widget.js
64 ms
jquery.matchHeight-min.js
56 ms
select2.min.js
53 ms
main.js
735 ms
chevron-down-orange.svg
293 ms
chevron-right-orange.svg
291 ms
QFP-Showreel-2023_v8.00_00_54_23.Still003.png
735 ms
QFP-Animation-Showreel-2023-UPDATE_v6.00_00_27_10.Still001.png
812 ms
LOr%C3%A9al_logo-copy.svg.png
517 ms
Louis-Vuitton-logo2.png
582 ms
1280px-Omega_Logo-copy2.png
710 ms
saboteur-og-image-138233-copy2.png
719 ms
POW-Feathers-with-CH-black-RESIZE-FOR-SITE.png
936 ms
Coca-Cola_Europacific_Partners_v2.png
1091 ms
Olympic_rings_without_rims-SIZED-FOR-SITE-v1.png
1132 ms
Unilever.svg-e1688649720717.png
1057 ms
Diageo-Logo-PNG2-e1673954607524.png
1082 ms
Yoox-Net-a-Porter.png
1243 ms
FHHq8LKWYAM2EEx.png
1349 ms
swoosh-logo-black-SIZED-FOR-SITE-v2.png
1471 ms
Mishcon-Logo-Alpha-SIZED-FOR-WEBSITE.png
1428 ms
GSK_logo_2022-SIZED-FOR-SITE-v2.png
1581 ms
Z100-full-logo-black-SIZED-FOR-WEBSITE.png
1571 ms
taylor-james-6673655_1646075206-SIZED-FOR-SITE.png
1662 ms
H_MasterLogo_Colour_POS_RGB_SIZED-FOR-SITE.png
1712 ms
diageo.jpg
2008 ms
DIAGEO-LOGO-BLACK-600x132.png
1757 ms
vlcsnap-2023-03-22-18h32m03s700-1080x608.jpg
1998 ms
UNILEVER-LOGO-600x664.png
1912 ms
Portfolio-Screengrab2023-03-20-16h17m57s085-1080x608.jpg
2072 ms
saboteur-og-image-138233-copy2-600x90.png
1976 ms
vlcsnap-2023-03-20-13h07m34s119-1080x608.jpg
1946 ms
1280px-Omega_Logo-copy2-600x293.png
2260 ms
IMG_9149-1080x720.jpg
2438 ms
0bf58c55-81a0-438f-a93f-9ab5c2268b52-1080x608.jpg
2475 ms
IMG_8984-1080x720.jpg
2257 ms
IMG_9241-1080x720.jpg
2187 ms
IMG_9149-600x400.jpg
2488 ms
0bf58c55-81a0-438f-a93f-9ab5c2268b52-600x338.jpg
2303 ms
Inter-Regular.woff
2550 ms
unicons-9.woff
80 ms
unicons-8.woff
102 ms
unicons-7.woff
138 ms
unicons-6.woff
138 ms
unicons-5.woff
100 ms
unicons-4.woff
101 ms
unicons-3.woff
180 ms
unicons-20.woff
139 ms
unicons-2.woff
138 ms
unicons-19.woff
217 ms
unicons-18.woff
138 ms
unicons-17.woff
139 ms
unicons-16.woff
140 ms
unicons-15.woff
138 ms
unicons-14.woff
175 ms
unicons-13.woff
176 ms
unicons-12.woff
175 ms
unicons-11.woff
175 ms
unicons-10.woff
176 ms
unicons-1.woff
176 ms
unicons-0.woff
175 ms
Inter-Medium.woff
2483 ms
Inter-Light.woff
2385 ms
Inter-SemiBold.woff
2327 ms
Inter-Bold.woff
2264 ms
IMG_8984-600x400.jpg
2137 ms
IMG_9241-600x400.jpg
2195 ms
Event-Production-Featured-Image-600x231.jpg
2216 ms
AdobeStock_576433058-600x400.jpeg
2302 ms
pexels-cottonbro-studio-6153354-600x400.jpg
1987 ms
DSC00090-150x150.jpg
2103 ms
IMG_9394-150x150.jpg
2132 ms
002-JPEG-Full-size-highest-quality-150x150.jpg
2056 ms
checkbox-circle-line.svg
1907 ms
quitefranklyproductions.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
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
quitefranklyproductions.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
quitefranklyproductions.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Quitefranklyproductions.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 Quitefranklyproductions.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.
quitefranklyproductions.com
Open Graph description is not detected on the main page of Quite Frankly Productions. 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: