6.6 sec in total
265 ms
4.7 sec
1.6 sec
Welcome to prettygeeky.com homepage info - get ready to check Prettygeeky best content right away, or after learning these important things about prettygeeky.com
Elegant, timeless, romantic wedding photos from Portland, OR wedding photographers. Also specializing in Engagments and Family Sessions.
Visit prettygeeky.comWe analyzed Prettygeeky.com page load time and found that the first response time was 265 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.
prettygeeky.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value3.9 s
53/100
25%
Value3.3 s
91/100
10%
Value120 ms
97/100
30%
Value0.319
36/100
15%
Value4.9 s
78/100
10%
265 ms
431 ms
300 ms
306 ms
307 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 73% of them (64 requests) were addressed to the original Prettygeeky.com, 20% (18 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Prettygeekyphotos.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Prettygeeky.com.
Page size can be reduced by 332.0 kB (7%)
4.7 MB
4.3 MB
In fact, the total size of Prettygeeky.com main page is 4.7 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 4.1 MB which makes up the majority of the site volume.
Potential reduce by 247.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 247.3 kB or 88% of the original size.
Potential reduce by 29.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. Prettygeeky images are well optimized though.
Potential reduce by 39.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 39.6 kB or 16% of the original size.
Potential reduce by 15.8 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. Prettygeeky.com needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 24% of the original size.
Number of requests can be reduced by 30 (48%)
63
33
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prettygeeky. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
prettygeeky.com
265 ms
prettygeeky.com
431 ms
cosmo-shortcodes.min.css
300 ms
slick.min.css
306 ms
contact-form-7.min.css
307 ms
flo-flex-builder-icons.min.css
326 ms
jquery-ui.min.css
317 ms
flo-forms-public.min.css
340 ms
style.min.css
721 ms
jquery.min.js
667 ms
jquery-migrate.min.js
599 ms
jquery.validate.min.js
612 ms
flo-forms-public.js
630 ms
css
30 ms
css
15 ms
flex-public.min.js
645 ms
core.min.js
845 ms
accordion.min.js
877 ms
tabs.min.js
881 ms
cosmo-shortcodes-lib.js
929 ms
slick.min.js
1006 ms
masonry.pkgd.min.js
973 ms
jquery.fancybox.min.js
1187 ms
index.js
1141 ms
index.js
1173 ms
datepicker.min.js
1273 ms
comment-reply.min.js
1250 ms
vendor.min.js
1408 ms
scripts.min.js
1448 ms
new-tab.js
1452 ms
prettygeeky_logo_72dpi-gold.png
457 ms
Tenderness.woff
262 ms
PN_yRfK9oXHga0XVzeoqghzQ.woff
37 ms
PN_yRfK9oXHga0XVqekqghzQ.woff
121 ms
PN_xRfK9oXHga0XdZsg5.woff
64 ms
PN_yRfK9oXHga0XVuewqghzQ.woff
127 ms
PN_yRfK9oXHga0XV3e0qghzQ.woff
80 ms
PN_yRfK9oXHga0XVwe4qghzQ.woff
79 ms
PN_yRfK9oXHga0XV5e8qghzQ.woff
64 ms
flo-icons.woff
758 ms
Objectivity-Medium.woff
273 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fvg-O.woff
51 ms
Derivia-Regular.woff
263 ms
NectoMono-Regular.woff
263 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7e8QL99U64.woff
50 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7eOQL99U64.woff
49 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7diR799U64.woff
50 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7dbR799U64.woff
92 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7c8R799U64.woff
89 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RkBI95.woff
89 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRkBI95.woff
91 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-NfNkBI95.woff
90 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-DPNkBI95.woff
92 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-a_NkBI95.woff
92 ms
lydia-taylor-wedding-bridalparty-062.jpg
80 ms
lydia-taylor-wedding-bridalparty-073.jpg
78 ms
lydia-taylor-wedding-bridalparty-022.jpg
81 ms
lydia-taylor-wedding-bridalparty-038.jpg
84 ms
lydia-taylor-wedding-bridalparty-142.jpg
78 ms
lydia-taylor-wedding-prep-069.jpg
85 ms
lydia-taylor-wedding-prep-097.jpg
82 ms
lydia-taylor-wedding-bridalparty-190.jpg
87 ms
lydia-taylor-wedding-prep-083.jpg
83 ms
lydia-taylor-wedding-prep-021.jpg
85 ms
lydia-taylor-wedding-prep-088.jpg
89 ms
lydia-taylor-wedding-prep-111.jpg
87 ms
lydia-taylor-wedding-prep-001.jpg
90 ms
lydia-taylor-wedding-bridalparty-173.jpg
95 ms
lydia-taylor-wedding-bridalparty-151.jpg
91 ms
lydia-taylor-wedding-bridalparty-164.jpg
97 ms
lydia-taylor-wedding-bridalparty-158.jpg
94 ms
lydia-taylor-wedding-bridalparty-183.jpg
94 ms
lydia-taylor-wedding-bridalparty-153.jpg
100 ms
lydia-taylor-wedding-bridalparty-156.jpg
97 ms
lydia-taylor-wedding-bridalparty-182.jpg
98 ms
lydia-taylor-wedding-bridalparty-188.jpg
99 ms
lydia-taylor-wedding-prep-003.jpg
184 ms
lydia-taylor-wedding-reception-030.jpg
185 ms
lydia-taylor-wedding-reception-036.jpg
181 ms
lydia-taylor-wedding-reception-032.jpg
182 ms
lydia-taylor-wedding-bridalparty-112.jpg
183 ms
lydia-taylor-wedding-prep-060.jpg
187 ms
lydia-taylor-wedding-bridalparty-056.jpg
185 ms
406 ms
jquery.fancybox.min.css
290 ms
style.min.css
350 ms
core-icons.min.css
297 ms
vendor-css.min.css
303 ms
prettygeeky.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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.
prettygeeky.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
prettygeeky.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Prettygeeky.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 Prettygeeky.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.
prettygeeky.com
Open Graph data is detected on the main page of Prettygeeky. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: