6.3 sec in total
627 ms
4.2 sec
1.4 sec
Welcome to quitefrankly.co.uk homepage info - get ready to check Quite Frankly best content right away, or after learning these important things about quitefrankly.co.uk
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 quitefrankly.co.ukWe analyzed Quitefrankly.co.uk page load time and found that the first response time was 627 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
quitefrankly.co.uk performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value3.7 s
59/100
25%
Value9.1 s
14/100
10%
Value630 ms
47/100
30%
Value0.003
100/100
15%
Value17.9 s
4/100
10%
627 ms
52 ms
372 ms
362 ms
57 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Quitefrankly.co.uk, 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.5 sec) relates to the external source Quitefranklyproductions.com.
Page size can be reduced by 935.7 kB (14%)
6.5 MB
5.6 MB
In fact, the total size of Quitefrankly.co.uk 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. 55% of websites need less resources to load. Images take 6.2 MB which makes up the majority of the site volume.
Potential reduce by 115.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 115.3 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 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 9.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. 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. Quitefrankly.co.uk 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. 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.
www.quitefranklyproductions.com
627 ms
uc.js
52 ms
style.min.css
372 ms
style.css
362 ms
css
57 ms
jquery.min.js
199 ms
jquery-migrate.min.js
294 ms
line.css
64 ms
select2.min.css
55 ms
js
96 ms
widget.js
61 ms
jquery.matchHeight-min.js
48 ms
select2.min.js
59 ms
main.js
520 ms
chevron-down-orange.svg
284 ms
chevron-right-orange.svg
308 ms
QFP-Showreel-2023_v8.00_00_54_23.Still003.png
726 ms
QFP-Animation-Showreel-2023-UPDATE_v6.00_00_27_10.Still001.png
814 ms
LOr%C3%A9al_logo-copy.svg.png
375 ms
Louis-Vuitton-logo2.png
526 ms
1280px-Omega_Logo-copy2.png
501 ms
saboteur-og-image-138233-copy2.png
707 ms
POW-Feathers-with-CH-black-RESIZE-FOR-SITE.png
794 ms
Coca-Cola_Europacific_Partners_v2.png
979 ms
Olympic_rings_without_rims-SIZED-FOR-SITE-v1.png
928 ms
Unilever.svg-e1688649720717.png
1201 ms
Diageo-Logo-PNG2-e1673954607524.png
1066 ms
Yoox-Net-a-Porter.png
1199 ms
FHHq8LKWYAM2EEx.png
1223 ms
swoosh-logo-black-SIZED-FOR-SITE-v2.png
1344 ms
Mishcon-Logo-Alpha-SIZED-FOR-WEBSITE.png
1309 ms
GSK_logo_2022-SIZED-FOR-SITE-v2.png
1555 ms
Z100-full-logo-black-SIZED-FOR-WEBSITE.png
1617 ms
taylor-james-6673655_1646075206-SIZED-FOR-SITE.png
1610 ms
H_MasterLogo_Colour_POS_RGB_SIZED-FOR-SITE.png
1404 ms
diageo.jpg
1708 ms
DIAGEO-LOGO-BLACK-600x132.png
1611 ms
vlcsnap-2023-03-22-18h32m03s700-1080x608.jpg
1820 ms
UNILEVER-LOGO-600x664.png
1889 ms
Portfolio-Screengrab2023-03-20-16h17m57s085-1080x608.jpg
2028 ms
saboteur-og-image-138233-copy2-600x90.png
1876 ms
vlcsnap-2023-03-20-13h07m34s119-1080x608.jpg
1865 ms
1280px-Omega_Logo-copy2-600x293.png
1803 ms
IMG_9149-1080x720.jpg
1905 ms
0bf58c55-81a0-438f-a93f-9ab5c2268b52-1080x608.jpg
2319 ms
IMG_8984-1080x720.jpg
2121 ms
IMG_9241-1080x720.jpg
2401 ms
IMG_9149-600x400.jpg
2310 ms
0bf58c55-81a0-438f-a93f-9ab5c2268b52-600x338.jpg
1972 ms
unicons-9.woff
81 ms
unicons-8.woff
92 ms
unicons-7.woff
134 ms
unicons-6.woff
135 ms
unicons-5.woff
134 ms
unicons-4.woff
135 ms
unicons-3.woff
134 ms
unicons-20.woff
134 ms
unicons-2.woff
135 ms
unicons-19.woff
135 ms
unicons-18.woff
135 ms
unicons-17.woff
135 ms
unicons-16.woff
136 ms
unicons-15.woff
136 ms
unicons-14.woff
171 ms
unicons-13.woff
135 ms
unicons-12.woff
136 ms
unicons-11.woff
136 ms
unicons-10.woff
170 ms
unicons-1.woff
171 ms
unicons-0.woff
171 ms
Inter-Regular.woff
2450 ms
Inter-Medium.woff
1889 ms
Inter-Light.woff
2309 ms
Inter-SemiBold.woff
1981 ms
Inter-Bold.woff
2304 ms
IMG_8984-600x400.jpg
2134 ms
IMG_9241-600x400.jpg
1746 ms
Bangalore-shoot-tea-picking-600x392.jpg
1930 ms
Event-Production-Featured-Image-600x231.jpg
1789 ms
AdobeStock_576433058-600x400.jpeg
2090 ms
DSC00090-150x150.jpg
1741 ms
IMG_9394-150x150.jpg
1988 ms
002-JPEG-Full-size-highest-quality-150x150.jpg
1683 ms
checkbox-circle-line.svg
1588 ms
quitefrankly.co.uk 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
quitefrankly.co.uk 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
quitefrankly.co.uk 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 Quitefrankly.co.uk 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 Quitefrankly.co.uk 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.
quitefrankly.co.uk
Open Graph description is not detected on the main page of Quite Frankly. 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: