16.6 sec in total
7.7 sec
8.8 sec
68 ms
Welcome to fomo.lv homepage info - get ready to check Fo Mo best content for Latvia right away, or after learning these important things about fomo.lv
FoMo.lv FoMo ir fotogrāfu, modeļu, stilistu utml ar foto saistīto portfolio un kontaktu vietne no iesācēja līdz profesionālim! Laipni lūgti!
Visit fomo.lvWe analyzed Fomo.lv page load time and found that the first response time was 7.7 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fomo.lv performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value6.3 s
10/100
25%
Value16.3 s
0/100
10%
Value160 ms
94/100
30%
Value0.07
96/100
15%
Value7.2 s
50/100
10%
7719 ms
478 ms
245 ms
252 ms
246 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 79% of them (27 requests) were addressed to the original Fomo.lv, 9% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.7 sec) belongs to the original domain Fomo.lv.
Page size can be reduced by 44.1 kB (13%)
338.3 kB
294.3 kB
In fact, the total size of Fomo.lv main page is 338.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 245.7 kB which makes up the majority of the site volume.
Potential reduce by 23.4 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 23.4 kB or 76% of the original size.
Potential reduce by 267 B
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. Fo Mo images are well optimized though.
Potential reduce by 18.9 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 1.5 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. Fomo.lv has all CSS files already compressed.
Number of requests can be reduced by 24 (83%)
29
5
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fo Mo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
fomo.lv
7719 ms
css.php
478 ms
style_advanced_photolightbox.css
245 ms
font-awesome.min.css
252 ms
animate.css
246 ms
insignia.css
248 ms
mootools-core-1.4.5-full-compat-yc.js
387 ms
mootools-more-1.4.0.1-full-compat-yc.js
638 ms
chootools.js
374 ms
core.js
377 ms
core.js
378 ms
smoothbox4.js
517 ms
scrollbars.min.js
518 ms
core.js
517 ms
core.js
518 ms
Observer.js
604 ms
Autocompleter.js
631 ms
Autocompleter.Local.js
634 ms
Autocompleter.Request.js
633 ms
SEAOMooVerticalScroll.js
664 ms
tagger.js
730 ms
fixWidthLightBox.js
755 ms
mdetect.min.js
763 ms
core.js
758 ms
js
58 ms
css
21 ms
loading.gif
139 ms
ga.js
13 ms
facebook-sign-in.png
128 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
23 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
24 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
25 ms
__utm.gif
34 ms
fontawesome-webfont.woff
268 ms
fomo.lv 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
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 IDs are not unique
fomo.lv 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
Browser errors were logged to the console
fomo.lv SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Fomo.lv 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 Fomo.lv 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.
fomo.lv
Open Graph description is not detected on the main page of Fo Mo. 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: